I'm trying to write a cool Games::Go::NNGS module. Well, I'm not sure what it'll be called, but that seems reasonable. I usually wait ot decide on a name until I have enough module to bother.
Heh. Anyway. I'll need to telnet in, and read/write from the socket. I'd prefer to have the module call function callbacks for events it detects.
It seems like a reasonably good place to use threads, but not everyone has perl compiled with threads. So I was looking at IPC::SysV. I remember reading that's flaky?
Is there a better solution to my telnet and let control pass back to the caller problem?
I found this mud client which sounded helpful, but my my $o = new Games::Go::NNGS would never return...
And so, I'm asking about IPC::SysV. Well, for an alternative. Am I missing a cool Net::Telnet::Callbacks or something? Should I use sockets or something? Should I just force people to recompile perl in order to use a threaded module?
I don't like that last one because of my Sendmail::Milter troubles... Recompiling perl on a P60 sucks.
update (broquaint): title change (was NNGS)
In reply to non-blocking TCP/IP client object using callbacks by jettero
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |