Re: IO::Socket vs. Socket vs. off-the-shelf telnet

A friend is running Perl on NT4 and the multiprocess model isn't as multiprocess as the one on say linux. The programs block at places that shouldn't block according to what you would expect normally in a multiprocess system. Since an earlier person said it works ok on their box not running Windows a weird blocking call where you wouldn't expect one may be the problem.

Telnet would actually get to run under another process and thus would work fine.

I think that this is related to one program (perl) only gets one real run per user i.e. if you run a browser and open a new window you still have only 1 browser. I think if you fork of another perl you still have 1 perl process and if it blocks all the perl 'processes' get blocked.

Comment on Re: IO::Socket vs. Socket vs. off-the-shelf telnet

Replies are listed 'Best First'.
Re: Re: IO::Socket vs. Socket vs. off-the-shelf telnet by abstracts (Hermit) on Aug 13, 2001 at 20:56 UTC
Hello Both server implementations are a single process single thread implementations. They handle one connection at a time, waiting for input and echoing it back. Fork-related problems on the Win32 platform should not be the problem since fork is not used. The comment about telnet running as another process is totally irrelevant since all programs mentioned were running as independent processes. Different perl programs do not share the same process the way some browsers do. Every program is run as an independent process, and just because one perl program is blocking does not mean all perl programs would block. Aziz,,,	[reply]

Replies are listed 'Best First'.

Re: Re: IO::Socket vs. Socket vs. off-the-shelf telnet
by abstracts (Hermit) on Aug 13, 2001 at 20:56 UTC

Both server implementations are a single process single thread implementations. They handle one connection at a time, waiting for input and echoing it back. Fork-related problems on the Win32 platform should not be the problem since fork is not used.

The comment about telnet running as another process is totally irrelevant since all programs mentioned were running as independent processes.

Different perl programs do not share the same process the way some browsers do. Every program is run as an independent process, and just because one perl program is blocking does not mean all perl programs would block.

Aziz,,,

[reply]