A hint on getting better luck with answers. People tend to be more likely to answer focussed questions. Broad, general questions are intrinsically hard to aswer because you don't know where to start or what level to pitch it at.

If you want to do RPC invocations in Perl then I would suggest using an Apache/CGI model because that network code is well understood and debugged. Failing that I would suggest starting with POE for the server. (Of course if you are nearly done, a rewrite to either model may not be worthwhile.)

Beyond that, without a specific socket or RPC question the best that anyone can say is that Lincoln Stein has this great book, there are examples in the Cookbook, and some examples in the documention. If there is something you can put your finger on that you don't understand, it might be worthwhile asking that.

As for a poor factoring between clients and servers, my gut feeling says that it makes sense for clients and servers to share code for part of the communication. I would therefore not be bothered that your clients use that even though you nominally thought that those routines belong in your server class.

Hopefully this is helpful. It isn't very concrete I know, but it is very difficult for me to find satisfactory answers to general questions.

In reply to Re (tilly) 1: Rather complicated OO (and RPC) question... by tilly
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.