#11 Add Dispatcher to IControllerContext/MaverickContext

closed
None
5
2005-02-09
2005-01-03
No

It would be nice to have the Dispatcher available
from with the controller via ControllerContext. The
following source change accomodates this:

Flow\IControllerContext.cs:18
Dispatcher Dispatcher
{
get;
}

Flow\MaverickContext.cs
14: protected Dispatcher theDispatcher;
47: this.theDispatcher = dispatcher;
56:
public Dispatcher Dispatcher
{
get { return theDispatcher; }
}
157:
String maxTransString =
this.theHttpContext.Request.Params
[this.theDispatcher.LimitTransformsParam];

Regards, Alexander Gräf

Discussion

  • Cort Schaefer

    Cort Schaefer - 2005-01-26

    Logged In: YES
    user_id=541173

    In adding support for forwarding, I came to the need to
    expose the dispatcher through IViewContext. I could add it
    to IControllerContext as well, but just curious as to why and
    if what you were trying to accomodate with this should be
    considered in what I am changing.

     
  • Alexander Graef

    Alexander Graef - 2005-01-26

    Logged In: YES
    user_id=1030440

    I made it available because I wanted to call
    Dispatcher.ExtractCommandName() in the Perform()
    method of the controller. You're right,
    ExtractCommandName is static, so the feature request
    is bogus... I didn't realize that at the first time I tried to
    retrieve the command name.

    Regards, Alex

     
  • Cort Schaefer

    Cort Schaefer - 2005-02-09
    • assigned_to: nobody --> corts
    • status: open --> closed
     
  • Cort Schaefer

    Cort Schaefer - 2005-02-09

    Logged In: YES
    user_id=541173

    Closed, since what was requested was later determined to not
    be needed by requester.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks