Hi, I haven't used Lift's comet support at all, but now it seems like a use case has popped up. I can do this with POA (Plain Ol Ajax), but, at least for me, it looks like CometActor might be a better fit. The use case is this:
We need to show a page containing a chart and some tables with data. The user should be able to filter, group, select new axis values etc in the page and the chart/table should be updated. All the views use the same underlying data, which will take some time (5-10s) to pull up initially. Changing views after initial load will reuse the data. So I was thinking to have a CometActor that holds the data and can render the specified view. The UI will send "view" messages that tell how to slice the data. The benefits from the actor solution as I see it are: 1) Can load initial data asynchronously 2) Can hold on to the data while the user is on the page 3) Page update is asynchronously, so the UI is perceived as faster Are these assessments correct? Or is this overkill? A few questions: 1) I assume each page get their own instance of the actor so they can hold their own data. Is this correct? 2) When is a CometActor shutdown? Sometime after the user navigates away from page? 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 /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en.
