Re: Server Client Architecture, best parctice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



my friend here forgot to add that it will be a pretty busy website
with lots of requests.
And i would also like to know if there are any other forms of
communication other than the 4 that my friend here specified. Anything
that you people think will be efficient.

On 11/17/05, Yaswanth Narvaneni <yaswanth@xxxxxxxxx> wrote:
> Hi!
>
> I would like to know what does the community think of the best
> architecture for server client communication and why? That is, if
> there is a server in C++ (say a game server) and the PHP has to 'read'
> data 'from' the server then what is the best form of communication?
>
> a) Shared Memory : Server opens the shared memory in write and the PHP
> scripts open it in read and gets the data
> b) TMPFS (just like shared memory): Server opens a file in tmpfs in
> write and PHP in read
> c) Databases: Server Updates a table in the DB and client reads from the table
> d) Files: Same as TMPFS
>
> Regards,
> Yaswanth
>
> --
> "In theory there is no difference between theory and practice.
> In practice there is." -- Fortune Cookie
>


--
Quitters never win and Winners never quit   -- Napolean Hill
In any moment of decision, the best thing you can do is the right
thing, the next best thing is the wrong thing, and the worst thing you
can do is nothing. --Teddy Roosevelt

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux