yes we have to serializing in another thread was to much over head and very
difficult code
(because of locking and synchronizing)

we save in a separate thread.

johan


On Wed, Aug 20, 2008 at 6:38 PM, John Patterson <[EMAIL PROTECTED]> wrote:

>
> It happens in the same thread.
>
>
> jwcarman wrote:
> >
> > Shouldn't the serialization be happening in another thread.  Are you
> > seeing performance hits because of it?
> >
> > On Wed, Aug 20, 2008 at 12:30 PM, John Patterson <[EMAIL PROTECTED]>
> > wrote:
> >>
> >> Is that the only reason?  I imagine most sites will be running on one
> >> server
> >> with no failover.  Is there a way to switch the serialisation of the
> >> current
> >> page off if failover support is not required?
> >>
> >>
> >> Martijn Dashorst wrote:
> >>>
> >>> Failover support needs the updates done by the ajax request.
> >>>
> >>> Martijn
> >>>
> >>> On Wed, Aug 20, 2008 at 6:13 PM, John Patterson <[EMAIL PROTECTED]>
> >>> wrote:
> >>>>
> >>>> Hi, this might be a really obvious question but... why are pages
> >>>> serialised
> >>>> for every ajax request?  I thought the latest page was always stored
> in
> >>>> the
> >>>> PageMap?
> >>>
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Page-serialisation-tp19072319p19073257.html
> >> Sent from the Wicket - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Page-serialisation-tp19072319p19073415.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to