----- Original Message ----- From: "Ing.Miroslav Kond?lka" <[EMAIL PROTECTED]> Date: Wednesday, October 27, 2004 2:34 am Subject: Re: Interactive socket client
> [EMAIL PROTECTED] wrote: > > > > > > > I think the problem is that your child dies before your parent > reads > > any data and closes STDIN+OUT. You can see that if you install > SIG > > CHLD handle. Don't forget that parent and child have same file > > handles, and execution order of process is never a sure thing. > The > > reason why it works on your unix box, is because you are not > fighting > > for time slices with other process's. Don't forget that on > Windows > > it's also not true parent/client environment. If you need more > help, > > don't hesitate to ask again. > > > > HTH, > > M Goland > > > > > How can i write legal interactive client like telnet under Win32? > I > don't understand, why don't work fork() under Win32. Miro, That has to do with Windows not implementing a true parent/child relationship. Perl emulates that relationship, so your code can be* cross independent. I also never herd of illegal telnet client, telnet is just a name of an open protocol. You can learn more about telnet by reading RFC's that are defined and related to telnet. Try using pipes [ perlfoc -f pipe ], to communicate between your processes, consider reading [ perldoc perlipc ]. Give it a try and we'll help you along. HTH, Mark > > TNX, Miro > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
