On 3/22/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > On 3/22/06, Mark Lowe <[EMAIL PROTECTED]> wrote: > > Population of indexed properties is a nice gift, but then I cant think > > of many situations where needing to scope anything that extreme is > > required. A bean with simple properties will do > > > > <jsp:useBean id="state" class="foobar.State" scope="session" /> > > <jsp:setProperty name="state" property="*" /> > > > > takes care of any simple properties > > I don't want to argue with you either :) I use session-scoped > actionforms, so it is simpler for me to stick everything related to a > resource in an actionform. > > > Another consideration is the increased popularity of xmlhttprequest to > > have the client make requests, if a front end updates from the server > > at any intervals. All you need is are users leaving a browser window > > open to increase the amount of active sessions on the container. > > I don't use Ajax autoupdate. But even if I did I would use session to > store Ajax-related stuff. Otherwise when a user hits Reload button, > all stuff is gone. Check out Backbase Pet Shop demo. Apparently these > guys don't use session. Pet Shop is a demo, but I would not want to > lose my shopping cart because of accidental refresh.
Yeah, i'd store ajax related requests the same as I would for non ajax requests as well.. And better an actionform than having n amount of attributes that are hard to keep track of. Cant say i see the value in a ajax shopping cart but interesting link. > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
