Loic and I discussed the idea of putting a registration cap on
tournaments. In other words, prohibiting, at the server side, a user
from registering for more than N tourneys. We decided that this is
actually a client side question. Summary of our discussion follows:
The feature was inspired by the idea that jspoker's GUI can currently
only display one table at the time, and generally speaking, various
clients in the future will have various limits on the number of tables
that can be displayed at once.
We then realized it was rather rude to stop the user from registering
for a tourney that will clearly run after their current one is done.
What's more, it's difficult to know exactly when a tourney will end
(even making a "worst case" estimate of the user getting to the last
two). So, our idea was to control the registration for no more than N
tourneys in H hours. This seemed better on the surface.
However, we ultimately decided against this feature. There is no way to
know for sure what the client's table-display limits will be in the
future, and different clients will have different limits. The client
should warn the user about *its* *own* limitations when the user tries
to register. of course, the client will have the same challenges of
knowing when a tourney will actually end, but it can just be a warning
and the user can proceed past it having been warned. A server-side
limit merely punishes more advanced clients, holding them back to the
lowest common denominator.
Some URLs of note on this issue:
* The original proposal for the feature server side:
http://ur1.ca/4bf
* Idea proposal for jspoker to do the job on the client-side:
http://ur1.ca/4bj
* Loic and I discuss the issue in IRC (URL not live until tomorrow):
http://pokersource.info/irc/[EMAIL PROTECTED]/2008-08-31.html
--
-- bkuhn
_______________________________________________
Pokersource-users mailing list
[email protected]
https://mail.gna.org/listinfo/pokersource-users
