Hi, In Wicket (AFAIK) we keeps only actual page reference in a web session, all other pages as serialized to a page store. AtmosphereBehavior registers itself as a listener to AtmosphereResource object. Because of this Atmosphere keeps references to all registered pages (until such resource expires). I think it could be a problem in high load applications: theses hard references could eat all memory.
What do you think: is it a problem or not (and I am wrong in this case)? -- Best regards, Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
