Lift 1.1-M7 and Terracotta

[Jonathan Hoffman]

Hi,

Has anyone had any recent success with using Terracotta to share
session state?

I've tried playing around with a simple lift app (1.1-M7) and
terracotta's sessions-configurator app.  It doesn't just work, but I
realized that's because Lift is hijacking sessions from the container
and managing them in SessionMaster.  I've tried configuring the root
object to be "net.liftweb.http.SessionMaster$.MODULE$" which is the
entire singleton, but that includes a lot of LiftActor stuff (and
terracotta complains about unlocked accesses to shared fields), and I
think really only want the "sessions" field.  I don't think i can make
"sessions" the root because its reference is overwritten every time a
new session is added.

Any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@...
To unsubscribe from this group, send email to liftweb+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

[bearfeeder]

On Fri, Nov 6, 2009 at 2:06 PM, jon <jonhoffman@...> wrote:

Hi,

Has anyone had any recent success with using Terracotta to share
session state?

I've tried playing around with a simple lift app (1.1-M7) and
terracotta's sessions-configurator app.  It doesn't just work, but I
realized that's because Lift is hijacking sessions from the container
and managing them in SessionMaster.  I've tried configuring the root
object to be "net.liftweb.http.SessionMaster$.MODULE$" which is the
entire singleton, but that includes a lot of LiftActor stuff (and
terracotta complains about unlocked accesses to shared fields), and I
think really only want the "sessions" field.  I don't think i can make
"sessions" the root because its reference is overwritten every time a
new session is added.

Any ideas?

Jon,

Can you send around the complaints TC has about sessions... I'll see where Lift is doing the offending thing and see if I can fix it.

I'll ping Jonas on this... he's the resident TC expert.

Thanks,

David
 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@...
To unsubscribe from this group, send email to liftweb%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

[Jonas Bonér]

Hi Jon.

Could you send me what you have so far and I'll try to take a look at it.
I'm pretty choked right now so I can't give it too many cycles but
I'll try to do my best :-)

Mail it to me directly: <my first name> AT jonasboner.com

/Jonas

2009/11/6 jon <jonhoffman@...>:

>
> Hi,
>
> Has anyone had any recent success with using Terracotta to share
> session state?
>
> I've tried playing around with a simple lift app (1.1-M7) and
> terracotta's sessions-configurator app.  It doesn't just work, but I
> realized that's because Lift is hijacking sessions from the container
> and managing them in SessionMaster.  I've tried configuring the root
> object to be "net.liftweb.http.SessionMaster$.MODULE$" which is the
> entire singleton, but that includes a lot of LiftActor stuff (and
> terracotta complains about unlocked accesses to shared fields), and I
> think really only want the "sessions" field.  I don't think i can make
> "sessions" the root because its reference is overwritten every time a
> new session is added.
>
> Any ideas?
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to liftweb@...
> To unsubscribe from this group, send email to liftweb+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>

--
Jonas Bonér

twitter: @jboner
blog:    http://jonasboner.com
work:   http://scalablesolutions.se
code:   http://github.com/jboner
code:   http://akkasource.org
also:    http://letitcrash.com

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

[Timothy Perrett]

This is really funny this should crop up - I've been having a conversation at Devoxx about cluster / distributing Lift.

David, one of the things i've been thinking is that it would be cool if we could potentially have some kind of abstraction for SessionMaster (a bit like we have http container providers) so that we could have a session master than for instance distributed with TC or Akka etc.

The only thing that is a little bit of a question mark is how one would serialise the state.

Cheers, Tim  

On 19 Nov 2009, at 20:41, David Pollak wrote:

>
>
> On Fri, Nov 6, 2009 at 2:06 PM, jon <jonhoffman@...> wrote:
>
> Hi,
>
> Has anyone had any recent success with using Terracotta to share
> session state?
>
> I've tried playing around with a simple lift app (1.1-M7) and
> terracotta's sessions-configurator app.  It doesn't just work, but I
> realized that's because Lift is hijacking sessions from the container
> and managing them in SessionMaster.  I've tried configuring the root
> object to be "net.liftweb.http.SessionMaster$.MODULE$" which is the
> entire singleton, but that includes a lot of LiftActor stuff (and
> terracotta complains about unlocked accesses to shared fields), and I
> think really only want the "sessions" field.  I don't think i can make
> "sessions" the root because its reference is overwritten every time a
> new session is added.
>
> Any ideas?
>
> Jon,
>
> Can you send around the complaints TC has about sessions... I'll see where Lift is doing the offending thing and see if I can fix it.
>
> I'll ping Jonas on this... he's the resident TC expert.
>
> Thanks,
>
> David
>  
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to liftweb@...
> To unsubscribe from this group, send email to liftweb+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>
> --
>
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to liftweb@....
> To unsubscribe from this group, send email to liftweb+unsubscribe@....
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

[bearfeeder]

On Fri, Nov 20, 2009 at 1:56 AM, Timothy Perrett <timothy@...> wrote:

This is really funny this should crop up - I've been having a conversation at Devoxx about cluster / distributing Lift.

David, one of the things i've been thinking is that it would be cool if we could potentially have some kind of abstraction for SessionMaster (a bit like we have http container providers) so that we could have a session master than for instance distributed with TC or Akka etc.

The only thing that is a little bit of a question mark is how one would serialise the state.

By question mark, do you mean a Godzilla sized, fire breathing, acid spitting beast of a question mark... 'cause that's the size of the problem... :-(
 

Cheers, Tim

On 19 Nov 2009, at 20:41, David Pollak wrote:

>
>
> On Fri, Nov 6, 2009 at 2:06 PM, jon <jonhoffman@...> wrote:
>
> Hi,
>
> Has anyone had any recent success with using Terracotta to share
> session state?
>
> I've tried playing around with a simple lift app (1.1-M7) and
> terracotta's sessions-configurator app.  It doesn't just work, but I
> realized that's because Lift is hijacking sessions from the container
> and managing them in SessionMaster.  I've tried configuring the root
> object to be "net.liftweb.http.SessionMaster$.MODULE$" which is the
> entire singleton, but that includes a lot of LiftActor stuff (and
> terracotta complains about unlocked accesses to shared fields), and I
> think really only want the "sessions" field.  I don't think i can make
> "sessions" the root because its reference is overwritten every time a
> new session is added.
>
> Any ideas?
>
> Jon,
>
> Can you send around the complaints TC has about sessions... I'll see where Lift is doing the offending thing and see if I can fix it.
>
> I'll ping Jonas on this... he's the resident TC expert.
>
> Thanks,
>
> David
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to liftweb@...
> To unsubscribe from this group, send email to liftweb%2Bunsubscribe@...
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>

> --

>
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to liftweb@....
> To unsubscribe from this group, send email to liftweb%2Bunsubscribe@....

> For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb%2Bunsubscribe@....

For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

[Timothy Perrett]

HAHA - yup, thats exactly what I mean!

There was work previously done on distributing with terracotta and it
was fraught with problems and exception cases. What are your thoughts
right now on serialisation (other than "its a nightmare")?

Cheers, Tim

> > The only thing that is a little bit of a question mark is how one would
> > serialise the state.
>
> By question mark, do you mean a Godzilla sized, fire breathing, acid
> spitting beast of a question mark... 'cause that's the size of the
> problem... :-(

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

[bearfeeder]

On Fri, Nov 20, 2009 at 3:39 PM, Timothy Perrett <timothy@...> wrote:

HAHA - yup, thats exactly what I mean!

There was work previously done on distributing with terracotta and it
was fraught with problems and exception cases. What are your thoughts
right now on serialisation (other than "its a nightmare")?

I need to write a tool that will walk the data structures in a LiftSession and see what's actually being captured and then figure out a serialization strategy for the data and the byte-code as well.
 

Cheers, Tim

> > The only thing that is a little bit of a question mark is how one would
> > serialise the state.
>
> By question mark, do you mean a Godzilla sized, fire breathing, acid
> spitting beast of a question mark... 'cause that's the size of the
> problem... :-(

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb%2Bunsubscribe@....

For more options, visit this group at http://groups.google.com/group/liftweb?hl=.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to liftweb@....
To unsubscribe from this group, send email to liftweb+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/liftweb?hl=.