A long conversion is to hold a session open over a few requests and flush it later right?
Wouldn't this cause an threading issue? Even when i bound the session to the current asp session id, i have no guarantee that the user opens multiple tabs or hits F5 10 times so that multiple requests from the same user accessing the not thread safe session? Steve Tyler Burd schrieb: > I wholeheartedly agree with this approach. Long conversations are a pain to > deal with, IMO. > > If the multi-page workflow is small enough you can carry along the data from > previous pages in hidden fields. If each step is large you might want to > persist each step in dedicated tables in a db. You would still need hidden > fields to track the ids of the saved steps. > > You CAN store the steps in the session, but that can cause it's own set of > problems. > > On Tue, Sep 15, 2009 at 9:20 AM, Jason Meckley <jasonmeck...@gmail.com>wrote: > >> I try to avoid long conversations and use intermediate dtos. any data >> required from the datab ase can be retrieved from a "standard" session >> at any point in the workflow. in the final step of the multi-page >> workflow I construct the domain objects and commit changes to the >> database. between pages the dtos are stored in session. using this >> approach there is no need for long running conversations. >> >> On Sep 15, 10:26 am, "kasvis...@gmail.com" <kasvis...@gmail.com> >> wrote: >>> Hi, >>> >>> I want to have simultaneous multiple long conversations. Looking at >>> the rhino commons code, I think long private conversation is the way >>> to go. But I am not sure how to go about implementing it. >>> >>> Currently rhino commons supports private conversations by tracking the >>> key in the Form variables or the querystring. The querystring will not >>> work for me because the conversation key will be generated in the form >>> load and I cannot add that to the querystring and hence will not work >>> during postbacks. >>> >>> The other option is using the Form variables, but the problem there is >>> that the ASP.NET renames the id when generating the html and so I >>> cannot retrieve the value thru the form variables. I was wondering if >>> storing the conversation key in ViewState is supported. >>> >>> Has anyone else tried to use private conversation with ASP.NET. I >>> would like to know how you went about implementing it. >>> >>> Thanks >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-dev@googlegroups.com To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
