Ari Zilka wrote:
>
> John,
>
> TC does not marshal objects in any way under user's control. It hooks
> into memory, watches for changes, and pushes what your business logic
> changes, on change. There is no way to invoke a marshaling task or
> fire an event that would force us to marshal the objects you want.
> (Well, there is but it is in the ManagerUtil classes and shouldn't be
> used directly).
>
>
I assume the bottle neck that Richard ran into is in TC's garbage
collection? So by artificially reducing the number of objects TC has to
manage (by serialising them into one object per page) he got around this. I
wonder if perhaps TC should do this transparently on the server (not the
client) if given the hint that certain classes always share the lifecycle of
their parent. Much like how Hibernate components are managed as a part of
their containing entity.
JD
--
View this message in context:
http://www.nabble.com/Terracotta-integration-tp18168616p18282665.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
