@David > Do you want everything to live in the same WAR file? ... No war at all, its a standalone app. Right now I have an embedded Jetty server with a registered jetty..RequestHandler. This app monitors machine tools on manufacturing floors, buffers the data, and provide a client http api for performing both one-time queries and for streaming data to the client. It connects to many tools and serves many clients. (A client may be performing predictive analysis, optimizing power loads, etc.)
I suppose what I'm looking for is to leverage Lift's request parsing and dispatching, concurrency/actor infrastructure, Jetty continuation impl, that kind of stuff. I need to keep the footprint as low as possible as the manufacturing shops don't like to install very powerful server boxes on the floor to run these agents. (For the interested, more info can found at http://mtconnect.org.) The app is written in Scala of course, but I'm a complete newbie wrt Lift. I haven't even read the book yet (hey, I just bought it the other day!), let alone dug into the code, so I could be asking for something outside the Lift's use-model. Hope this context clarifies. -barry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
