Hi Daniel! Your idea sounds quite reasonable to me. Have you got any demo code?
Regards, chriss Daniel Frisk wrote: > > > A third option, which from my POV is perhaps the most elegant, is to > roll your own page store that serializes the pages instantly after the > request. The serialization have special hooks to replace entites or > whatever that you would prefer to have as LDM with a placeholder that > just stores the type and id when serialized. When/if the page is later > deserialized you get the entity fresh from your object repository > (cache). > > Why is this elegant? You get the programming model of push with the > benefits of pull without writing any code for model proxies. I have > communicated this idea before but nobody but me seems to prefer it, > I'm actually surprised :-) > > // Daniel > jalbum.net > -- View this message in context: http://www.nabble.com/Open-Source-projects-using-Wicket-tp25917713p25923855.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
