WebSockets will fulfill most of your needs, except browser compatibility (it only works on limited browsers).
But its use is really straightforward. If you can control which web browser to use. Yesterday we successfully demoed a prototype Android app with a Seaside backend, it uses Seaside, REST, and live updates with WebSockets sent to Chrome running in a Tablet. The whole stack is there for you to use* :) Regards, * Given the proper ConfigurationOf* :) Esteban A. Maringolo 2013/4/9 Ingo Hohmann <[email protected]> > Hi Sven, > > thank you for the answer. > > The specific reason for comet is that it is described in the seaside book. > :-) > > I might think about using for a changes streamm that us pushed to the > client, but there is no real need at the moment. > > > Kind regards, > > Ingo > > > > > On 04/09/2013 11:50 AM, Sven Van Caekenberghe wrote: > >> There is an implementation of WebSockets on top of Zinc, and there is a >> streaming Seaside adaptor. Is there a reason you need Comet specifically ? >> > > >
