in reply to Instant Messaging Protocol

I would use Net::EasyTCP

It has built in encryption, password logons, and can send hashes easliy in both directions. It isn't suitable for heavy traffic, but can probably handle 10 simultaneous connections nicely, as long as there were no large file transfers, since it uses IO::Select and not forking.

Replies are listed 'Best First'.
Re: Re: Instant Messaging Protocol
by Eyck (Priest) on Jan 06, 2004 at 12:49 UTC

    Yeah, it's great, but all it provides is 'inteligent' socket, ie - you get encryption and compression transparently, and it uses it's own tiny protocol for negotiating that, but you still need to figure out some IM protocol on top.