Squaretoilet

Event Source and Connection Limits

The new eventsource feature in browsers I think is far underrated. It removes the ugly aspects of comet and makes it easy. Maybe too easy.

I had never run in to a browser ajax connection limit until I learned of this little gem. Here I am though running smack faced in to a limit of a mere 6 connections. I suppose the solution we came up with is not necessarily good for every case but it certainly has worked for us.

The first message contains an event source uuid that the server can then retrieve the erlang process with when requests come in. Requests are then sent to the server to subscribe or unsubscribe to specific channels of information. Each subscription itself has a unique id so that duplicate subscriptions may be allowed. All of this allows for the event source to act like a channel containing many other channels of information all streaming to the browser in a subscription manner. This could be chats, rss feeds, really anything. The basic idea is there though that many channels of subscribed information over one. Really though this is all to avoid what I feel is a poorly defined browser limitation. If anyone thinks this might be useful to them I can certainly try and package it up and put it on github to share!

There are comments.

Squaretoilet

Other articles

Slow Erlang Consumer

Starting an Erlang Program

Other articles

social