Error: cannot handle extended pids and ports

Fri Apr 1 23:27:25 CEST 2005

What about using spread? there is a python binding and I thought there was/is an erlang binding.

You could have various levels of readonly multicast data streams,
that a process could subscribe to and you could even create an api that allowed others to build apps that plug in to a given public feed.

* public info about server status, active games, player stats, rankings, etc (the lobby server/[service] you talk about on your site)
* public info about game X (watch game)
* public info about player Y (watch all games for a certain player, I don't know if current poker servers have this function)
* player-only info about game X (participate in game)
* server-to-server only info about games, internal server states etc.

As new servers, processes or clients start up they would either subscribe to the appropriate streams or create new ones and register 
them with a stream directory service.
For poker it seems very little info is transfered upstream so those could probably be tcp connected per request - so placing a bet or 
getting cards, etc would be an atomic tcp interaction. Even a single erlang node should be able to handle 10's or 100's of 1,000's of 
player upstream interactions that way.

Vance Shipley wrote:
> "Joel Reymont" <joelr1@REDACTED> writes:
> }
> } Now, you wouldn't have a totally untested Reliable UDP implementation
> } lying around, would you? :)
> Since RUDP has been superceded by SCTP that leads us back to the gen_sctp
> discussion.  :)
> SCTP isn't really the answer for you as although the server side is easy
> to provision getting SCTP support into clients is unlikely for many years.
> I wouldn't try and implement a full blown RUDP in erlang.  I'm sure you
> can build an application specific protocol on top of UDP fairly easily
> which would satisfy your requirements.  Stevens(*) has a section entitled
> "Adding reliability to UDP applications" which you might want to read.
> As he points out many existing applications have implemented this; DNS,
> SNMP, TFTP & RPC are given as examples.
> 	-Vance
> (*)

More information about the erlang-questions mailing list