-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>
>> A new machine will be created and a new network installed on it..
>> The table names, variants and betting structure (holdem, 5/10 no
>> limit).
>
> Are the default table names ok ?
>
Yes.
>> There must be two bots playing on the first two tables. The poker
>>  server must be configured with auto-refill set to the best buyin
>> for the 5/10 no limit betting structure.
>
> Does someone now the best buy in for 5-10-no-limit ? 2000 ?
>
>
The best buy-in can be found in the corresponding poker-engine XML file.
>
>
> Are you ok relying on a mercurial nested clone of jpoker in
> /usr/src like unique.pokersource.info, rather than the packaged
> version ?
>
Yes.
>
>
> If we use PackerPokerCreateAccount, the problem is that currently
> it is bypassing newly introduced pokerauth (see
> pokerservice.py:5796). sql = "INSERT INTO users (created, name,
> password, email, affiliate) values (%d, '%s', '%s', '%s', '%d')" %
> (seconds(), packet.name, packet.password, packet.email,
> packet.affiliate)
>
> An alternative would be to use PacketPokerLogin, and userInfo to
> set the email if the user creation succeed.
>
My opinion is that we should go with PacketPokerCreateAccount because
this bug does not show in the current use case. And fill a bug report
against the packet to remember the bug you just found.

Cheers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko/+0IACgkQ8dLMyEl6F21IYACgp4u4QTDbVfhaGETdyU6hPtIX
q6AAn3K7n3SUhO3B2Jf8QNe0zNOFa/ON
=AQiU
-----END PGP SIGNATURE-----

begin:vcard
fn:Loic Dachary
n:Dachary;Loic
org:pokersource
adr:;;12 bd Magenta;Paris;;75010;France
email;internet:[email protected]
title:Senior Developer
tel;work:+33 9 51 18 43 38
tel;cell:+33 6 64 03 29 07
x-mozilla-html:FALSE
url:http://dachary.org/
version:2.1
end:vcard

_______________________________________________
Pokersource-users mailing list
[email protected]
https://mail.gna.org/listinfo/pokersource-users

Reply via email to