Hi Eduardo,

If you are not talking about Comet style of usage of HTTP, but just a long 
streamed representation, then Restlet should just work
fine.

If you are looking for streaming video protocols like RTMP (Flash), then you 
should look for pointers in this RFE:

"Add RTMPT server connector"
http://restlet.tigris.org/issues/show_bug.cgi?id=562

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : [email protected] [mailto:[email protected]] 
Envoye : jeudi 29 janvier 2009 17:10
A : [email protected]
Objet : Streaming media resources over HTTP

I'm using restlet to manage a media catalog of music files. I have a nice 
restful API for getting the media information, e.g.
ID3Tags for MP3 files, and so on.

I have a server side application, not running in a web application server, that 
embeds the restlet container.

I also have a Java media client application that uses this service and can play 
audio files across the network by having a web
server stream the audio files to the client over HTTP.

Currently I simply stream the audio files directly from URLs on a separate 
Tomcat instance but I'm now thinking why isn't that just
a restful GET request to my existing server-side application?

Does anyone have any opinions or pointers on this, is it an appropriate usage 
of the restlet API - is this sort of long-lived
requests for streaming of audio files something that should be done with a 
restlet approach? Is there anything I should look out
for? I guess I'm concerned about resource usage, long running requests and 
timeouts.

Any thoughts would be greatly appreciated.

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1069260

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1075273

Reply via email to