Hi, I see no problem here. Wicket-Atmosphere keeps the pageId, not the page: https://github.com/apache/wicket/blob/3eba671c0770b0167f2d83ebf8924b28917316c9/wicket-experimental/wicket-atmosphere/src/main/java/org/apache/wicket/atmosphere/EventBus.java#L253
Later uses it at https://github.com/apache/wicket/blob/3eba671c0770b0167f2d83ebf8924b28917316c9/wicket-experimental/wicket-atmosphere/src/main/java/org/apache/wicket/atmosphere/AtmosphereRequestHandler.java#L76 Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jul 20, 2015 at 1:54 PM, Daniel Stoch <[email protected]> wrote: > 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: [email protected] > For additional commands, e-mail: [email protected] > >
