I realize that long conversation should be avoided as much as possible. I was wondering about how nhibernate sessions are stored in Burrow when used in long conversations so as to not interfere when opening requests in multiple tabs.
I am currently using Rhino tools and am really happy with it. The only limitation is that you can have only 1 long conversation whereas in Burrow it clearly mentions in the wiki that it supports multiple concurrent long conversations. Can anyone shed some light on how Burrow accomplishes it. thanks On Mar 5, 11:08 am, Nexus <[email protected]> wrote: > I personally don't like long conversations as they tend to cover the > real issues with web development and that is following > > So you select a customer in a long conversation, you retrieve its > details, page get transmitted to client, user goes to toilet, > meanwhile customer gets removed (updated), and your postback > happens !! > > What do you want to do as a developer to fix this ? > > Suppose the customer was deleted ????, use saveorupdate ??? > > As a side note these sort if things also means you putting something > into viewstate, sessionstate (in my example the customer) > > General advice, use a decent 2nd level cache and retrieve your object > again, much easier > > Kind regards -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
