I'd second the IO::Socket idea (or third, or fourth...)
I'll even justify it for you:

from my perspective, if you can keep the server simple (all the clients use the same protocol to access it) then it keeps debugging down to a minimum. It also splits it up functionally, so each component does one thing, and (hopefully) does it well.
The soap idea is similar in principal, and might be a good idea. (not sure what the protocol is like, but I've heard good things about it) If its sufficient to get your data moved, then go for it. no point doing work you don't have to after all. if your other clients can use it, then congrats, you've just found a drop in networking module.

In reply to Re: Communications Between a Game Server and Web Front End by fuzzysteve
in thread Communications Between a Game Server and Web Front End by dooberwah

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.