Hi Pieter, Good question.
For 1) you might want to try implementing HTML5 Server-Side Event which relies on streaming representations as well. For 2) you should indeed try streaming representations. Some have experienced issues with network buffering though, but it should work. Another RESTful way moving forward will be to rely on HTTP/2.0 server-side push http://tools.ietf.org/html/draft-ietf-httpbis-http2-02#section-4.3 Otherwise, you will have to rely on another technology such as WebSockets and integrate it with RF. Maybe there is space for a WebSockets extension based on HTTP/2.0 semantics. It would probably require an evolution of Restlet API though, Best regards, Jerome -- http://restlet.org http://twitter.com/#!/jlouvel 2013/5/11 Pieter Martin <pietermar...@lavabit.com> > Hi, > > What is the current recommended strategy with restlet to implement some > form of a server side push in a browser environment. > > In our case we have 2 use cases for this. > > 1) A standard publish/subscribe requirement for sending messages to the > client. > 2) We need to simulate a server side ssh or telnet terminal session via > the browser. > > For 2 I think it might be better and simpler to use restlet's current > streaming representation support. > > BTW, really enjoying working with the restlet api. > > Thanks > Pieter > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055303 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3055973
