Table of contents
    1. 1. Goals
    2. 2. Breaking changes

    A place to keep track of planned changes for Dream 3.0 as well as tracking existing pain points

    Goals

    • Split into distinct assemblies to let users mix and max features
    • Make default scenarios work by naming conventions and use attributes only as explicit option
    • Make synchronous use cases simpler (since async has certain penalties right now)
    • Improve documentation
    • Create simple stories for starting to use Dream's components
    • Provide more options for DreamServices
      • Per request Controller classes
      • Full IoC integration
      • Injection of any request or container instance at feature level

    Breaking changes

    • Synchronous Plug calls will no longer throw
      • i.e. use Wait() instead of Block() behavior
      • old behavior will be available via app.config setting
    • Uri related features moved from XDoc to client assembly as extension methods
    • Various DreamContext dependent behaviors removed from DreamMessage and Plug
    Tag page
    You must login to post a comment.

    Copyright © 2011 MindTouch, Inc. Powered by