Hi Marius, I would like the conversations contained within each tab. If I were to use just a Session variable then the user's state/data would "collide" and therefore cause unexpected behavior.
This link does a better job of describing how conversations solve this problem: http://www.informit.com/content/images/9780131347960/samplechapter/0131347969_CH08.pdf. Thanks, Bryan On Jan 22, 12:29 pm, Marius <marius.dan...@gmail.com> wrote: > The conversation context could be kept in a SessionVar. When your > context terminates (say user clicked a button). You can attach a > cleanUp function to the SessionVar (see registerCleanupFunc) so when > your context terminates you can just call remove() on your SessionVar > > Would that help or I'm just misunderstanding your case? > > Br's, > Marius > > On Jan 22, 6:24 pm, Bryan <germ...@gmail.com> wrote: > > > Does lift offer conversation contexts? If so, could someone provide > > me with an example. > > > I am not sure if conversation context is the proper term, but I am > > using this term as it is used by JBoss Seam. A partial description > > would be an "approach that allows state to be scoped to a unit of work > > and automatically handles memory cleanup when a conversation is no > > longer in use." This would allow users to work in multiple tabs. > > Keeping the back button working during this process would be a *huge* > > plus. > > > Thanks, > > Bryan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
