>> I implemented this by hooking in to serialization, just checking
>> each object
>> in ObjectOutputStream.replaceObject and
>> ObjectInputStream.resolveObject.
>> Also had to use my own PageMapEntries to get a suitable hook. Might
>> work as
>> an idea for your implementation perhaps?
>
> That's a cool idea for individual projects. For Wicket in general
> however, the problem would be that it wouldn't work for every session
> store (it wouldn't for instance for HttpSessionStore which doesn't
> serialize on each request). Also, 1.3's default session store
> serializes on each request, but does not reuse that serialized
> instance until the back button is used (or if you're doing session
> replication and come in through another node I guess). Are you sure
> your detachment works like you think it does?
Well... I haven't actually hooked into the SessionStore but instead
have implemented a special PageMapEntry that stores a serialized page
with my "special serialization" (hooked in by overridden
getPageMapEntry(...) in my BasePage). The special serialization takes
place when the page is put into the pagemap. If the pagemap entry
should be stored to disk later it is an object with serialized data
that gets serialized again. I'm pretty sure it works as I intended and
it might be generalized. The programming model sure is very nifty.
// Daniel
jalbum.net
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
