1) I assume each page get their own instance of the actor so they can
hold their own data. Is this correct?
Yes.
No, it's not correct. There's one CometActor of a given type/name per
session.
Sorry for this. I just hat the relation one page - user (==
session) in mind...
--
You
I have a similar use case and from my experience using a CometActor is
just great for this.
1) I assume each page get their own instance of the actor so they can
hold their own data. Is this correct?
Yes.
2) When is a CometActor shutdown? Sometime after the user navigates
away from page?
On 2 March 2010 15:09, ced docpom...@googlemail.com wrote:
3) How do I get access to the CometActor instance on the page? I need
to send a message to it from a function bound to e.g. an ajaxSelect
You need another Actor that dispatches messages to your CometActors.
Say you have
On Tue, Mar 2, 2010 at 6:09 AM, ced docpom...@googlemail.com wrote:
I have a similar use case and from my experience using a CometActor is
just great for this.
1) I assume each page get their own instance of the actor so they can
hold their own data. Is this correct?
Yes.
No, it's not
I agree with David and think a simpler AJAX approach would be better.
From my work with lift-flot I know it's definitely possible (see the
lift-flot AJAX example). You can even do your plotting entirely in
Javascript and only use Lift to return data requested via AJAX, which
I've done for updating
