in reply to Socket between internal processes
A quick look at permfunc:bind gives the following information.
bind SOCKET,NAME Binds a network address to a socket, just as the bind system call does +. Returns true if it succeeded, false otherwise. NAME should be a pac +ked address of the appropriate type for the socket. See the examples +in Sockets: Client/ Server Communication in the perlipc manpage
You can find the reference in the above here. It contains several good examples.
It also has this rather interesting comment:
If you ever see code that does anything like explicitly setting $AF_IN +ET = 2, you know you're in for big trouble: An immeasurably superior +approach is to use the Socket module, which more reliably grants acce +ss to various constants and functions you'll need.
This can be found here Socket though it is quite likely that this is a part of your stadard distribution It is in mine.
|
|---|