Hehe, no worries, I love problems that solve them selves :)

On Fri, Jul 10, 2009 at 7:48 PM, Loic Dachary <l...@dachary.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Loic Dachary wrote:
> > Hi,
> >
> > In the context of a multiplayer online poker game (
> > http://pokersource.info/ ) I'm trying to figure out the proper way
> > to display the gender of a player in the JavaScript client that
> > will display as a gadget ( http://jspoker.pokersource.info/ ). The
> > poker server knows nothing of the gender of a user, it is only
> > concerned with its chips and the action at the table ;-)
> >
> > At first I thought the JavaScript client could use the JavaScript
> > opensocial / gadget API to query the gender of a player sit at the
> > poker table. Assuming this information is made public by the
> > opensocial container, it seemed logical. However, there does not
> > seem to be a function to do that. And when Johan (another developer
> > of the pokersource software) pointed me to this post
> >
> >
> http://groups.google.com/group/opensocial-api/browse_thread/thread/e61103dee8f23d40/a8001b7b1cbf7c2c?lnk=raot
> >
> >
> > I realized that I was probably thinking backward.
> >
> > Since each poker player will install the poker application and
> > therefore grant access to some of its data to the poker server,
> > maybe the proper way would be for the poker server to collect the
> > user gender. The JavaScript poker client would then run a
> > makeRequest call to the server, asking for user information
> > collected from the opensocial container in order to change the CSS
> > of the player according to her/his gender.
> >
> > I would very much appreciate you opinion : am I thinking right ?
> >
> Please ignore this mail. It all comes from a misunderstanding. Thanks
> for not flaming me ;-)
>
> Cheers
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkpXft8ACgkQ8dLMyEl6F20wKwCeJTwLEGeXRqJqxM1F3AW+7PRB
> BfUAnibgp2kHCzFPEWR/O+krhc7mprZE
> =GNCz
> -----END PGP SIGNATURE-----
>
>

Reply via email to