in reply to Node removed.
Depending on your audience, you may want to give your API more of an OO feel:
Aoother suggestion is to used one of the canned POE wheels to implement your server. That way, your code becomes scalable, using multiple threads.use Dispatcher qw(RequestDispatch ReadData SendData); my $d = new Dispatcher({host => "192.168.1.1",port => "1440"}, "data1", "data2", "data3"); foreach my $type (qw(data1 data2 data3)) { print "RECIEVED for ", $d->read()->type , "\n\n"; # $d->read returns a Dispatcher::Record object, which + has a "type" } my $rec = $d->NewRecord({type=>"data4"}); # Returns a Dispatch +er::Record object associated with $d $rec->send ("DATA"); # The Record already know what port, serv +er, and type to use. $d->Port (1440); $rec->send("More Data on port 1440");
Compliments on the clean code!
"Choose a job you like and you will never have to work a day of your life" - Confucius
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: RFC: dispatcher UPDATED, now comes with API
by Trizor (Pilgrim) on Apr 08, 2007 at 17:32 UTC |