|
bugsbunny has asked for the wisdom of the Perl Monks concerning the following question:
hi,
does anyone know of a module which can do the client/server communications for me, so that i can concentrate on the real task..
I will need mostly to excahge messages ...
any ideas and solutions ...
of cource also the ability of a such script to run like deamon (there was a such module on CPAN afaik)
thanx in advance |
•Re: client/server tcp/ip module ?
by merlyn (Sage) on Feb 12, 2003 at 12:26 UTC
|
| [reply] |
Re: client/server tcp/ip module ?
by PodMaster (Abbot) on Feb 12, 2003 at 09:56 UTC
|
POE seems to be a popular choice ...
POE
::Component
::Client
::TCP
::Server
::TCP
MJD says you
can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.
|
| [reply] |
Re: client/server tcp/ip module ?
by Ryszard (Priest) on Feb 12, 2003 at 09:43 UTC
|
I've used Net::Server very effectivly in the past. The documentation is a little difficult to comprehend straight up, (or at least was for me at the time) however with a little tenacity, i've got something that works really well.
This is only one half of you're requirement, i would think client communication could be handled quite effectively by IO::Socket | [reply] |
Re: client/server tcp/ip module ?
by hiseldl (Priest) on Feb 12, 2003 at 13:41 UTC
|
Take a look at "Advanced Perl" in the networking chapter for an implementation of a client/server. You can find the example scripts at http://examples.oreilly.com/advperl/; when you unzip the file, look in the Networking directory for the Msg.pm and RPC.pm. You should be able to get an idea of how to use them from the demo scripts.
--
hiseldl
What time is it? It's Camel Time!
| [reply] |
Re: client/server tcp/ip module ?
by zentara (Archbishop) on Feb 12, 2003 at 18:37 UTC
|
Go to cpan and get Net::EasyTCP.
It does it all by passing hashes back and forth, and has built in encryption. It is the way to go as far as I'm concerned. | [reply] |
|
|
The security protocols used by EasyTCP are... um... suboptimal. Its password authentication mechanism is vulnerable to eavesdropping. The symmetric encryption keys are passed in the clear if you're not careful. And there's no protection at all against active attackers. If encryption is a real requirement, you should use something else.
| [reply] |
|
