Re: socket port

Thank you so much Jim. -Chris

Re: socket port

On Aug 30, 2012, at 6:46 AM, Chris Stinemetz wrote: > Hello List, > > I am creating a program, where for the first time, I will be reading > in data from a socket port. > > I am a bit confused about how to print the processed data while still > reading in data from the p

Re: socket port

Thank you Peng. Are there any other suggestions from the list? Thanks in advance, Chris

Re: socket port

You might take a look at AnyEvent Intro: http://search.cpan.org/~mlehmann/AnyEvent-7.02/lib/AnyEvent/Intro.pod 在 2012-8-30，下午9:46， Chris Stinemetz 写道： > Hello List, > > I am creating a program, where for the first time, I will be reading > in data from a socket port. > > I

socket port

Hello List, I am creating a program, where for the first time, I will be reading in data from a socket port. I am a bit confused about how to print the processed data while still reading in data from the port. Thus far, I have only processed data from a file where the while loop ends when EOF

Re: Code Socket Port... Read In and sent out to perl script

On Mar 5, 2004, at 4:55 PM, david wrote: James Edward Gray II wrote: # do work here, like: while (<$socket>) { print; } # or whatever construct such as this should almost never be used in a network application. this will potentially hung your application when the client and the server

Re: Code Socket Port... Read In and sent out to perl script

James Edward Gray II wrote: > > # do work here, like: > while (<$socket>) { print; } # or whatever > construct such as this should almost never be used in a network application. this will potentially hung your application when the client and the server use a different EOL sequence. w

RE: Code Socket Port... Read In and sent out to perl script

> OK, you owe me a beer :~) Note that this has zilch security or anything to > prevent DoS type attacks, so caveat emptor... Should I send the ups red label ;) > > server.pl > - > #!/usr/bin/perl > > use strict; > use IO::Socket::INET; > > my $n = 0; > > my $sock = IO::Socket

Re: Code Socket Port... Read In and sent out to perl script

Paul Kraus wrote: > > I need a daemon listening on a port. I need a client side script that just > takes piped input in and then dumps it out to a file on the other server. > > I need more then that but the rest I can handle in the allocated time. > > Example > Files sendtextfile (arguments) ser

Re: Code Socket Port... Read In and sent out to perl script

On Mar 5, 2004, at 2:21 PM, Paul Kraus wrote: I hate to ask for code but I am kind of in a crunch to finish a project. I have the network programming with perl but it's just too much to read by tomorrow night :) Here's an example server, pretty much right out of the Perl Cookbook: #!/usr/bin/p

RE: Code Socket Port... Read In and sent out to perl script

Bob Showalter wrote: > ... > warn "Received connection from $host, writing to $file\n"; > open F, ">$file"; Stick some error checking in there :~) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Code Socket Port... Read In and sent out to perl script

Paul Kraus wrote: > I hate to ask for code but I am kind of in a crunch to finish a > project. See below. > > I have the network programming with perl but it's just too much to > read by tomorrow night :) Buy the Perl Cookbook. It has good examples for this kind of thing. > > I need a daemon

Code Socket Port... Read In and sent out to perl script

I hate to ask for code but I am kind of in a crunch to finish a project. I have the network programming with perl but it's just too much to read by tomorrow night :) I need a daemon listening on a port. I need a client side script that just takes piped input in and then dumps it out to a file on