Dear all, We have an existing RESTful web application that involves clients downloading multiple streams of data simultaneously. Our current implementation is based on servlets and we are experiencing scalability problems with the number of threads involved in serving multiple large data streams simultaneously. I recently came across Restlet and was attracted by the potential to use NIO under the hood to enable more scalable large file transfers.
In our case we are not necessarily serving large files that already exist on disk: we are essentially creating the files ourselves on the fly (so they are of unknown length when the file transfer starts). I was wondering if anyone could offer advice on how to support the serving of such data streams through Restlet in a scalable manner (ideally without creating a new thread on the server for each file transfer)? Thanks in advance, Jon -- -------------------------------------------------------------- Dr Jon Blower Tel: +44 118 378 5213 (direct line) Technical Director Tel: +44 118 378 8741 (ESSC) Reading e-Science Centre Fax: +44 118 378 6413 ESSC Email: [EMAIL PROTECTED] University of Reading 3 Earley Gate Reading RG6 6AL, UK --------------------------------------------------------------
