This answer is easy, I think: "Write a simple streaming socket server." Put that one thing on the other end of your paid-for pipe and make very sure that it can never violate their paid-for license agreement. Anyone else who wants to receive the data need simply connect to the server’s published internal IP address: it will immediately receive an exact copy of everything that comes in. (Maybe one of the always-connected clients is another simple daemon that writes everything that it hears to a local database for posterity.) The internal server is ready to accept an unlimited number of internal connections ...
“The various things that you then connect to this multi-outlet software water spigot” are yours to design. nginix, Mojo, have at it. Because they’re all now "downstream." They all receive data from a Perl multiplexer that will never violate the license agreement.
-
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 How to display code and escape characters
are good places to start.
|