Actors are local to the JVM. Scala also has RemoteActors but we don't
really use them. For a lift app in a cluster environment we have to
have sticky sessions concept and the reason is that functions bound to
a session and mostly the references they are holding are not
serialized distributed. So
Thanks, that was very useful, to enable sticky variables i would do
something like (explain here
http://wiki.stax.net/w/index.php/Application_Clustering
) that?
So bottom line? An actor can send a message an actor that is living in
another JVM using sticky variables(or anything else) (sorry i
On Jul 10, 10:40 am, DFectuoso santiago1...@gmail.com wrote:
Thanks, that was very useful, to enable sticky variables i would do
something like (explain
herehttp://wiki.stax.net/w/index.php/Application_Clustering
) that?
So bottom line? An actor can send a message an actor that is living
Cool, thanks, this pretty much solves the question =)
On Jul 10, 12:54 am, marius d. marius.dan...@gmail.com wrote:
On Jul 10, 10:40 am, DFectuoso santiago1...@gmail.com wrote:
Thanks, that was very useful, to enable sticky variables i would do
something like (explain
Refering to why i want to know this:
Im using stax because it's free, they are pretty cool and lift/scala
worked out of the box pretty fast(i was having some issues getting
some hosting for whatever i do in my free time with lift/scala). They
have a cluster option right now(still, free) so, they
