Re: Communications Between a Game Server and Web Front End

Howdy!

Right off the top of my head, I'd go for the socket based communications. That frees you from the requirement that the web front end and the server be on the same box.

Decoupling is good. It lets you isolate the two parts. It makes it easier to try different clients.

You will want to clearly document the communications between the parts.

yours,
Michael

Comment on Re: Communications Between a Game Server and Web Front End

Replies are listed 'Best First'.
Re: Re: Communications Between a Game Server and Web Front End by IlyaM (Parson) on Nov 28, 2001 at 05:11 UTC
I second it. It makes sense to have network protocol since you are going to have several different clients (as you have said). Just want to note that IO::Socket could be too low level. If you don't have any serious perfomance requirements take a look at SOAP. There exist very nice module SOAP::Lite which makes writting SOAP servers and clients very simple.	[reply]
Re: Re: Re: Communications Between a Game Server and Web Front End by jepri (Parson) on Nov 28, 2001 at 05:55 UTC
Take it one step further and write a SOAP client program that you can distribute. No web needed! Go soap! ____________________ Jeremy I didn't believe in evil until I dated it.	[reply]