At first I read this and thought "Great, the worst of both solutions!". But thinking it through, this actually sounds pretty good. Everything runs on one box, so the architecture problems disappear. No more rsh. Performance will be improved over my proposed monolithic solution (these are mostly SMP boxes).
Best of all, I get to keep using the socket code I wrote that I'm so proud of. :)
Don, thanks for your comments too. Yes, I am somewhat nervous about how complex the system is becoming! I can't say too much about the application, but this isn't something that I would know how to solve with a web-browser.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.