It happened in revision 707, but the comment doesn't explain why - "Patch from Christian Crowhurst Long Conversations in UoW".
As I understand it, for a long conversation we store the UoW in the session between web requests, so I can't see why we don't do that during a redirect. 2009/3/21 Ayende Rahien <[email protected]>: > I think there was a good reason for that, check the svn log, to see why this > is happening. > > On Sat, Mar 21, 2009 at 8:39 AM, Alex Scordellis <[email protected]> > wrote: >> >> In UnitOfWorkApplication, the unit of work is closed (or saved for the >> next request in a long conversation) in an event handler attached to >> the HttpApplication.PostRequestHandlerExecute event. I've discovered >> that this event is not fired when a request is redirected - see >> >> http://alexscordellis.blogspot.com/2009/03/aspnet-doesnt-fire-postrequesthandlerex.html >> >> Was it a deliberate choice not to close the unit of work when a >> redirect occurs? I've noticed that the method attached to the event is >> called UnitOfWorkApplication_EndRequest, suggesting that it used to be >> attached to the EndRequest event, which is fired on a redirect. >> >> Alex >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
