What you will want to do is manage the water marks on the wheel. And since Client::TCP doesn't readily expose the wheel, you will probably end up needing to implement your own client. Or you can step into the kitchen and manage the wheel yourself.
See POE::Wheel::ReadWrite's HighEvent/LowEvent (http://search.cpan.org/~rcaputo/POE-1.0000/lib/POE/Wheel/ReadWrite.pm) And also look at the evolution of a POE server from scratch (sorta) to give you an idea of the intermediate steps (http://poe.perl.org/?Evolution_of_a_poe_server) On Mon, Mar 31, 2008 at 7:21 PM, John R. <[EMAIL PROTECTED]> wrote: > I may have a problem overloading a device connected to a TCP server. I > am not 100% sure the problem is sending requests too fast, but it seems > like a good debugging step. So, if I have a loop in which iteration has > (ultimately) a "$_[HEAP]->{server}->put( $msg . "\n" )", what is the > POE way of doing this? I am pretty sure "sleep" is not the answer as > that causes all sorts of weirdness (as I expected). > > John > -- Nicholas R. Perez
