On Sat, 25 Feb 2006 11:45:36 -0600
"Matt Sickler" <crazyfordynamite@xxxxxxxxx> wrote:
Hi,
> What is it that your trying to accomplish? This will help us suggest
> what to use.
It's a middleman between a source of data and a requester of data.
Both of these being already existing entities using TCP. The middleman
has to work using different data and request sources in one
configuration (eg. not many at the same time) and also, it has some
other tasks to perform such as modifying requests to be forwarded,
keeping logs, keeping statuses, writing data to disk, so on so forth.
Thus, what I saw was two TCP interchangeable components for the
middleman 'system', surronded by some others for logging purposes, for
saving data, etc... Ideally I would have liked for all of them
sessions and/or components to exchange data internally using POE
messages while TCP would have been kept to communication with the
outside requests and data source. Thus an API of sorts could have been
developed and used by eventual other TCP interfaces to different data
sources and data requests.
Sounds straightforward enough, and I got quite a good bit working but I
stumbled on this transmission of POE messages to the TCP server from
another session that has no TCP connection with the server, being only
a simple session.
BTW, not because there are not enough examples in the cookbook (there
are quite a bunch and they're all interesting) but a nice O'Reilly book
all dedicated to POE would be very super. You know, about 400
pages ... ;-)
As with a lot of other things Perl, POE is very interesting to work
with. A loop including the Prima Toolkit would be quite nice. Prima
is a Perl graphical toolkit, quite simple and not 100% perfect, that has
a visual builder and is portable.
Thanks for all comments - it's appreciated !
Can we write a petition to O'Reilly ? ,-)
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|