poker-network
poker-network includes a poker server, a client library, an abstract user interface library, and a client based on it. The server deals the cards and checks the user actions using a poker game engine (poker-engine). It listens on a TCP/IP port and understands its own specific protocol. The persistent information is stored in a MySQL database. The client library implements the poker-network protocol for the client. The abstract user interface library provides a framework based on the client library and suited to implement a user friendly client.
| Tags | Games/Entertainment |
|---|---|
| Licenses | AGPL |
| Operating Systems | OS Independent |
| Implementation | Python |
Recent releases
- 14 Apr 2009 13:08
Changes: Support for backoffice clients was added. Bugs were fixed.
- 27 Dec 2008 10:11
Changes: Bugfixes.
- 23 Dec 2008 09:18
Changes: The REST interface was completed. Nine translations were added. A proxy server with authentication capabilities was implemented. Test coverage was improved. An authentication plugin infrastructure and example were implemented.
- 29 May 2008 12:42
Changes: Improved REST support.
- 17 May 2008 06:49
Changes: Complete JSONP support and custom session names. User names can be up to 50 characters. A new packet was implemented: PacketPokerBuyInLimits(Packet). The buy-in boundaries for "game_id" are now in the range ["min","max"]. An optimal buy-in is suggested in "best".
