Thanks for responding, Aran, Tyler, and Daniel. I appreciate your
thoughtful advice.
I am planning to use SSE. It's for some slow server-side operations
that typically take 1-3 minutes or so, where I want to give the user
near-real-time updates on what's happening. I don't need full duplex
or
On Thu, Nov 14, 2013 at 10:12 PM, Daniel Friesen wrote:
> Basically in the end your best bet is probably to just use something
> other than PHP for this.
> The native implementations for both Socket.IO's and SockJS' servers are
> in Node.JS.
> So that's probably the best bet for doing this.
> You
On 2013-11-14 5:22 PM, Tyler Romeo wrote:
> On Thu, Nov 14, 2013 at 6:12 PM, Lee Worden wrote:
>
>> Has anyone messed with this? Any code I should crib from, or advice or
>> cautionary tales? Also, if it develops into something useful, I could
>> split it out for others to use.
>
> I have not me
On Thu, Nov 14, 2013 at 6:12 PM, Lee Worden wrote:
> Has anyone messed with this? Any code I should crib from, or advice or
> cautionary tales? Also, if it develops into something useful, I could
> split it out for others to use.
I have not messed with it personally, but I think it is a good
Wouldn't WebSocket be the better choice for a full duplex channel?
On 14/11/13 21:12, Lee Worden wrote:
> In the MW extension development I'm doing, I'm thinking of writing
> some operations that use [[Comet_(programming)]] to deliver continuous
> updates to the client, rather than the Ajax patter
In the MW extension development I'm doing, I'm thinking of writing some
operations that use [[Comet_(programming)]] to deliver continuous
updates to the client, rather than the Ajax pattern of one request, one
response.
Has anyone messed with this? Any code I should crib from, or advice or
c
