On a complete aside ... I have been very pleased with RPC::Any as a basic framework for a recent project. (It is not an exact fit to this requirement, but a very fine framework for RPC. Just sayin’ FYI.)
Edit: I have also learned to add the following features, as part of the descriptive information that goes back and forth (if it’s not already provided by the protocol): - A version-number. If the format changes, change the number. You never know when an old version of something is still out there wanting to talk to you.
- A randomly generated string, produced by the client, which the host must return verbatim. Excellent for matching up requests with responses. (But don’t be tempted to use it as a reliable-identifier on the host-side.)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.
|
