Re: Lightweight session management
I see the point, but still I expect this to be a frequent use-case for Facebook App iframe integration. There, you get the OAuth-Token/Session Secret/whatever only for the initial iframe request, and then usually put them into the session (at least this is suggested by the PHP examples). And at least the marketing guys hope that there will be some number of visits on such an app :-) Anyway, thanks for the reply; I'll use bind() on the session and see how things go. I've done stress testing, and it looks ok memory-wise; but reading about how much effort is spent into statelessness, I was wondering if I am missing something. Would you recommend bothering about being stateless at all? Quoting nino martinez wael : Yeah it's prone to fall under YAGNI and if not use time on it when it becomes a problem.. 2010/7/28 Igor Vaynberg load test it and see if it becomes a problem before spending any cycles on a solution. -igor On Wed, Jul 28, 2010 at 7:54 AM, M. Hammer wrote: > Hello, > > in my application I would like to have user sessions for storing some data > (mostly related to tracking which pages a user has visited), but otherwise > stay stateless as long as possible to keep memory consumption low. Is there > any provision in Wicket for such a scenario? I could run two session > managements in parallel, but I'd rather reuse Wicket's facilities. > > On a related note, my back-of-the-envelope-calculations somehow suggest that > I should not bother anyway, as I'd run out of CPU time about the same time I > run out of memory. Can someone share some experience? My app is rather lean, > but runs a CMS that is similar to Brix, so it is made up from many > components, but only some AJAX and form elements are actually stateful. > > Thank you very much, > Moritz > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Lightweight session management
Yeah it's prone to fall under YAGNI and if not use time on it when it becomes a problem.. 2010/7/28 Igor Vaynberg > load test it and see if it becomes a problem before spending any > cycles on a solution. > > -igor > > On Wed, Jul 28, 2010 at 7:54 AM, M. Hammer wrote: > > Hello, > > > > in my application I would like to have user sessions for storing some > data > > (mostly related to tracking which pages a user has visited), but > otherwise > > stay stateless as long as possible to keep memory consumption low. Is > there > > any provision in Wicket for such a scenario? I could run two session > > managements in parallel, but I'd rather reuse Wicket's facilities. > > > > On a related note, my back-of-the-envelope-calculations somehow suggest > that > > I should not bother anyway, as I'd run out of CPU time about the same > time I > > run out of memory. Can someone share some experience? My app is rather > lean, > > but runs a CMS that is similar to Brix, so it is made up from many > > components, but only some AJAX and form elements are actually stateful. > > > > Thank you very much, > > Moritz > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Lightweight session management
load test it and see if it becomes a problem before spending any cycles on a solution. -igor On Wed, Jul 28, 2010 at 7:54 AM, M. Hammer wrote: > Hello, > > in my application I would like to have user sessions for storing some data > (mostly related to tracking which pages a user has visited), but otherwise > stay stateless as long as possible to keep memory consumption low. Is there > any provision in Wicket for such a scenario? I could run two session > managements in parallel, but I'd rather reuse Wicket's facilities. > > On a related note, my back-of-the-envelope-calculations somehow suggest that > I should not bother anyway, as I'd run out of CPU time about the same time I > run out of memory. Can someone share some experience? My app is rather lean, > but runs a CMS that is similar to Brix, so it is made up from many > components, but only some AJAX and form elements are actually stateful. > > Thank you very much, > Moritz > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Lightweight session management
Hello, in my application I would like to have user sessions for storing some data (mostly related to tracking which pages a user has visited), but otherwise stay stateless as long as possible to keep memory consumption low. Is there any provision in Wicket for such a scenario? I could run two session managements in parallel, but I'd rather reuse Wicket's facilities. On a related note, my back-of-the-envelope-calculations somehow suggest that I should not bother anyway, as I'd run out of CPU time about the same time I run out of memory. Can someone share some experience? My app is rather lean, but runs a CMS that is similar to Brix, so it is made up from many components, but only some AJAX and form elements are actually stateful. Thank you very much, Moritz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
