title: How do streaming resources fit within the RESTful paradigm?
body: <p>With a RESTful service you can create, read, update, and delete resources.  This all works well when you're dealing with something like a database assets - but how does this translate to streaming data?  (Or does it?) For instance, in the case of video, it seems silly to treat each frame as resource that I should query one at a time.  Rather I would set up a socket connection and stream a series of frames.  But does this break the RESTful paradigm?  What if I want to be able to rewind or fast forward the stream?  Is this possible within the RESTful paradigm?  So: <strong>How do streaming resources fit within the RESTful paradigm?</strong></p>
  
  <p>As a matter of implementation, I am getting ready to create such a streaming data service, and I want to make sure I'm doing it the "best way".  I'm sure this problem's been solved before.  Can someone point me to good material?</p>