So an example use of a socket would be, say, a script that would listen on a socket (?) and notify me in response to a message from a particular cgi being executed on my webserver?
I guess I'm not sure where anyone would use this...
A socket or your example?
Your example can be handled in better ways then listening for CGI responses.
Why not have the CGI just notify you? Via SMTP? Via WWW logs? Via syslog? Via file output you collect and process autonomously?
Or the WWW server itself configured to "tattle" about things...
So, in answer to your example - yes; you can have a Perl script wait on a Socket and get data -- so long as the "other" application is written to "speak" to your "listener."
HTH/Sx
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
