in 1.3 with the new Disk based store we dont need by default the window detection yes so it is turned off by default.
Also the detection is pretty good but not completely solid! It will always be very hard to really detect and play nicely under all circumstances For example if you have 1 transaction in 1 tab and then the users does on a link or form: open in new tab? what then? should the transaction be transported? Also are those transactions really down the drain database transactions? or just in memory transactions? long database transactions is a really really bad idea.. There are only a very few databases that play nice in this area (oracle and postgresql) the rest are just horrible (no Multi Version Read Consistency) Maybe in 1.5 we will transform the pagemap to a first class Window object but i dont know if we can really make that 100% reliable johan On Thu, Aug 21, 2008 at 10:25 AM, Martijn Dashorst < [EMAIL PROTECTED]> wrote: > On Thu, Aug 21, 2008 at 10:22 AM, John Patterson <[EMAIL PROTECTED]> > wrote: > > I was just considering storing the unit-of-work in the PageMap meta-data. > > I haven't used that. Session is more in my comfort zone ;) > > > What exactly is the problem with detecting the different browser windows? > > When does it break? > > Automatically detecting new windows is non-trivial, and is turned off > by default IIRC. I'm not intimate with the details. Johan and Matej > wrote that part and should be able to shine some light on this > subject. > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
