I'm writing a little set of modules to provide services for distributed computing/P2P networks. I want the modules to be as abstract as possible - they should be useful for different message formats and transports, although they have their own default format and transport.

There are 2 ways to achieve this:

1. Write a superclass with default methods for sending, receiving, encoding and decoding messages, and let subclasses override these methods. This is used by e.g. IO::Socket and HTTP::Daemon.

2. Write a class with optional callback hooks for the above tasks. Unless the hooks are defined (as subrefs) by the client, use the default methods. Something like this method is used by e.g. WWW::Robot.

Has anyone got any opinions on which is better, and when?

David

dave hj~

In reply to subclass or hooks? by dash2

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.