Hi, first, if you want, you can still use traditional sessions with RIFE, you just have to turn raw access to the servet API on: http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#setProhibitRawAccess(boolean).
However, we think there are better ways. You can for instance not use a session but stateful elements instead, with or without continuations: http://rifers.org/wiki/display/RIFE/Stateful+components Another solution, which is very traditional, is to just pass an ID around of your shopping cart and interact with a cart bean that's stored in the database. RIFE makes this very easy using global variables and the generic query manager. Now, authentication and authorization is a very vast topic, and RIFE has a lot to offer there. For instance, we have what we call 'behavioral inheritance' or '3D flow declarations'. These are basically sites that you can layer on top of other sites and trigger going to the lower level based on certain criteria (like being authenticated). The great thing here is that if that trigger doesn't happen, the context that was intended for a lower site is preserved while a user is navigated around in an upper site (registration, logging in, password retrieval, you name it ...). When the user finished his business in the upper site, the flow falls down and restores the initial context, resuming the original intent of the user's action. The result is for instance that when you post a form and your authentication session timed on, you didn't lose the information, you can just login again and your form will be posted with all the data you sent. You can find a lot more information about all this on the wiki. Hope this helps, Geert On 6/2/07, LoneWolf <[EMAIL PROTECTED]> wrote: > > Hi. > For a typical web application, you would like to store some data in > the session scope (shopping cart, authenticated user object), and to > store other data in request scope. > I understand that RIFE templates are just content I manipulate. > Does RIFE has equivalent concepts ? > Typically, I use a filter to guard the protected areas, if the a > visitor is trying to add an item to his cart, the filter should check > if a cart object exists in the session scope, if not, redirect the > visitor to login page. > What is RIFE approach to this case ? > Thanks for your time. > > > > > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
