I’m looking specifically at the case where the server gets restarted during a long-poll request. In this case, there’s no response and the Faye clients simply stop polling. At a minimum, there should be a way to configure the behavior in this case (e.g. “retry every 10 seconds”)

Also, I’d prefer to have a way to adjust the polling frequency of the Faye.XHR readystate check. (10ms strikes me as a bit aggressive.)

… oh, and also, you might consider doing this:

if (self._xhr.readyState !== 4) setTimeout(handleState, 10)

… instead of using setInterval. It’s simpler, and avoids potential issues with multiple setInterval calls getting queued up if CPU performance lags for whatever reason.

If you are interested in the result of my work, please see my article, Cross Browser CSS Transforms – even in IE.

One thing I wanted to mention was that using your recommended approach of setTimeout(func, 0); does not work properly.

The ‘i’ variable gets closured properly but in the context of setTimeout function, it is still being changed by the for loop. So essentially all the callbacks throw errors as ‘i’ is still changing and will most likely be equal to listeners.length.

We remedied this by wrapping the setTimeout function argument in its own auto invoked function as declared below.

    setTimeout(function(x){
        return(function(){
            // code here using x
        });
    }(i), 0);

Cheers,

Brent.

// Remote client
client = new Faye.Client('http://example.com/faye');

// Local client
server = new Faye.NodeAdapter(options);
client = server.getClient();

And use the client just like you would in a browser.

The approach of using the ‘document’ is a neat one, and I’ve seen a mixin you created a while back (http://gist.github.com/204012) that does just that. Would love to have this kind of functionality rolled in to Prototype’s core.

Mike, for the record, any true event handling system written in JavaScript will need to rely on host objects for error handling (you don’t want an error thrown by an event handler to stop the event being dispatched to the other event handlers). Dean Edwards wrote a great article on the subject a while back: http://dean.edwards.name/weblog/2009/03/callbacks-vs-events/

Prototype’s event model uses the DOM, other systems will rely on `setTimeout` to call handlers. Either way, you’re bound to the browser environment.

That said, if you consider the `document` object as as the broker in a publisher/subscriber pattern, you can very well use Prototype’s custom event system outside of the DOM.