I should point out that this server/client setup is not to use any web servers. The reason being that it requires extra resources on the server (to make sure the web server doesn't bog down the machine). Basically, the only thing I really need to do is setup a socket server, sit it on a port, and wait for connections (using an infinite loop and IO::Select). When a socket comes alive and is ready for reading, then I can capture the data, wrap it in an eval(), and write the results back to the socket. This method seems to me like a better way to go, since it won't be as resource intensive (I can easily have it close after an amount of time and re-run it at a scheduled time). The only thing I haven't figured out is how to remember which socket is being read and which socket will be written to after the eval is completed. I think a little more diving into socket programming will help me to overcome that.

The POE set of modules also seems like a good idea. The only thing I worry about is implementation of my code over the wire using that module (I was reading the docs for the base POE class, and it didn't say anything about OO... I might have to read further into it). In most cases, WWW stuff would be a good idea if this was over the entire net. Since this is a LAN based project, I think a webserver with all of the XML and stuff is quite an overkill (not to mention that WWW stuff is pretty foreign to me in the first place). Simple RPC is all I need.

Theodore Charles III
Network Administrator
Los Angeles Senior High
4650 W. Olympic Blvd.
Los Angeles, CA 90019
323-937-3210 ext. 224
email->secon_kun@hotmail.com

In reply to Re: Re (tilly) 1: Rather complicated OO (and RPC) question... by Necos
in thread Rather complicated OO (and RPC) question... by Necos

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.