in reply to Communications Between a Game Server and Web Front End

Several people have said that I should is the SOAP module instead of IO::Select. I was wondering why they say this: is it because of performance or portability?

-Ben Jacobs (dooberwah)
"one thing i can tell you is you got to be free"

  • 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 29, 2001 at 01:22 UTC
    It is because of simplicity. IO::Socket provides you with low level protocol. Basically you can just read and write strings from a stream. You will have to roll your own high level protocol for communication between game server and client. You mentioned that you want several different clients. It means that unless they are all written in Perl they all will need their own libraries for handling of this high level protocol.

    With SOAP you already have high level protocol which is portable across different OSes and programming languages. Basically it a protocol which allows you to do RPC (function and method calls). SOAP::Lite is very convinient librariy which makes it completly transparent in Perl. See yourself. Read SOAP::Lite Guide.

    As for perfomance SOAP::Lite will be probably slower than your own protocol over IO::Socket. But it acceptable price in most cases unless you have very strict perfomance requirements.

[reply]

In Section Meditations