- From: Evan Prodromou <evan@status.net>
- Date: Tue, 18 Sep 2012 16:54:36 -0400
- To: public-fedsocweb@w3.org
- Message-ID: <5058DF8C.3070208@status.net>
On 12-09-17 02:09 PM, Martin Atkins wrote: > On 09/17/2012 07:07 AM, Evan Prodromou wrote: >> Has anyone else looked into using Websockets for server-to-server >> distribution of activities? >> >> Seems like it could be very efficient. >> > > I'm curious to hear what advantages you consider Websockets to have > over tranditional sockets. Aside from the explicit message framing, is > there any functional difference beyond a bare TCP socket? I didn't have any in mind, but if there were drinks on the line I could probably make up a few plausible-sounding ones. * WebSocket happens over the same port 80 as "regular" HTTP. You don't have to have a separate listener for a different ad-hoc port. * You could use the same stack for handling C2S and S2S realtime communications (similar to how we use HTTP for C2S and S2S in e.g. OStatus). * WebSocket is cool. -Evan -- Evan Prodromou, CEO and Founder, StatusNet Inc. 1124 rue Marie-Anne Est #32, Montreal, Quebec, Canada H2J 2B7 E: evan@status.net P: +1-514-554-3826
Received on Tuesday, 18 September 2012 20:54:59 UTC