From: David Vallner <david@...>
Date: 2006-12-10T01:17:25+09:00
Subject: Re: [ONLINE GAME] Ruby Core + Php FrontEnd (open)

--------------enigD1391864393F89C8266C6645
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Flaab Mrlinux wrote:
> So this is what i've thought; I'm gonna have a Web Based Php Front-end
> for the players to comunicate with the game. And a Ruby Core program
> sinchronized with Cron to be launched every 3 minutes for example. That=

> Core will do all these things i can't do from Php, catching MySql files=

> that tells it what to do, do it, and update those MySql fields which ma=
y
> need updating.
>=20

Concurrency errors beware. Whatever the frontend, how do you plan to
communicate with the backend? Since this is write-mostly database work,
what architecture do you plan to use?

You might want to consider two database layers, one to store things that
happen between these three-minute cycles (to provide immediate feedback
to players), some action log (message queue) you'd sort through
depending on what the evaluation cycle is (think M:tG turn phases), and
then a second DB layer with the long-term state of the game.

Hrm, did I get taken away on an ill-informed architecture rant? Ah well ;=
P

David Vallner


--------------enigD1391864393F89C8266C6645
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFeuGJy6MhrS8astoRArTMAJ0W2wYNWzZbvFjcyMmwvms7IWDWewCfUe+3
PBhjL1MKSs/Jkz3X8KO43gs=
=DAli
-----END PGP SIGNATURE-----

--------------enigD1391864393F89C8266C6645--