"Michael Oschmann" <[EMAIL PROTECTED]> writes:
> Example: Player goes to table 102 (is observer) he/she doesn't have enough
> money, so I want to disable the seats buttons (make them invisible). Once
> they have requested money from the currency server, I want the available
> seats to be displayed.
> And to do this I need packetpokerseats.
I suggest you clearly separate the data structures used for
your poker display client in two :
1) the game state that gets updated when you receive the
packets from the poker server. This data structure should
not contain any display information.
2) the display state that relates to the game state
What you're trying to do is only cosmetic and you should not
rely on the server to implement it.
Note that the server, when acting in EXPLAIN mode, relieves the
client from understanding the rules of poker. The client only need to
store the current state of the game and update it when a new packet is
received. While in a given state, the client has enough information to
display all the user needs to see, down to the number of chips going
from a side pot to one of the players who tied.
Such a mode requires more (from x2 to x10) bandwidth but makes it
easier to implement a client. If you rely on the server to retreive the
game state instead of storing it locally, I think you are going to create
serious performance problems because you will increase the bandwidth used
by the client even more.
Cheers,
--
+33 1 76 60 72 81 Loic Dachary mailto:[EMAIL PROTECTED]
http://dachary.org/loic/gpg.txt sip:[EMAIL PROTECTED]
Latitude: 48.86962325498033 Longitude: 2.3623046278953552
_______________________________________________
Pokersource-users mailing list
[email protected]
https://mail.gna.org/listinfo/pokersource-users
