Roger, I'm not exactly sure what you are attempting to do, but, it sounds as if you could possibly use http sessions for your "pooled" connections. Cocoon does support sessions, via the session logicsheet, which makes it easy to store data associated with any particular session.
If your clients can make web like (URL) requests to the "socket", in this case the web server/cocoon, you should easily be able to take advantage of cocoons capabilities for your application. Whether or not cocoon is appropriate for your situation would really depend on how fast the server has to respond to requests. While cocoon is quite fast, especially when accessising cached URI's, it would not be as fast as a proprietary (in-house) client/server setup (unless the in-house app is poorly written)... Also, initial startup time for cocoon (after a reboot - or re-initializing cocoon) can require up to 30 seconds on my PIII 800 (1 gig ram)... Hope this helps... Stan Roger I Martin PhD wrote: >Would anyone recommend using Cocoon to transfer and render data from >server-side connections to stand-alone applications automatically running >equipment for monitoring and administration purposes? Does the framework >have functionality to connect with a local port on the server and keep the >connection open for multiple transfers and rendering? Similar to pooling >for database connections, but instead pooling the socket connection for >mulitple requests for current data in memory from another server-side >application. Some data I can put into a database and use esql in xsp but >there is a need to check on data inside the running application which is >aquiring data from external hardware devices. The purpose of looking at the >data inside the running application instead of just the database is to >determine if the application is processing data correctly and observe >intermediate data (Intermediate data is data either too large or there is no >reason to store in a database). > >We are looking for a remote solution because the equipment is running inside >a environmental clean room. We have done it with stand-alone-client/server >sockets but are now wanting to use a browser interface published from a >Cocoon-like framework. > >Roger > > > > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
