Interesting question on a number of levels. Are you using HTTP as the transport mechanism, or your own protocols following REST principles? In the absence of a correct and bounded Content-length header property, you will have problems with a number of client and server libraries, and typically HTTP client and server libraries have some upper bound timeout for the duration of an HTTP request/response cycle. So you would need to be very specific in the selection of your client and server connectors and possibly do some extra configuration on both sides to make sure your stream-based representation would work. If that were all taken care of, I would say any of the stream-based Representation classes, or your own extensions thereof, would be fine.
You could also conceivably use REST principles (addressability, statelessness, uniform interface) and Restlet to manage your own protocol(s) -- I am thinking of stuff like SIP and RTP -- but that's hardly trivial. ----- Original Message ----- From: "Erik Vullings" <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, October 12, 2007 8:40:12 AM (GMT-0500) America/New_York Subject: Newbie question: How to stream data between RESTlets Hi, I have two RESTlets, one acting as a sensor, the other as a detector. The sensor serves data that is consumed by the detector. Since the sensor RESTlet continuously generates data, I want to stream this data to the detector(s) RESTlet. What's the best way to do this? And what kind of representation should the sensor generate if we are dealing with simple data ( e.g. numbers). If I get a good solution, I promise to put it on the new Wiki. Thanks, Erik
