Re: [PHP] hmm sockets (again)
Mukul Sabharwal wrote: > Hi, > > I might have missed a follow up or your original > message, but have you tried socket_set_blocking() Mukul, Yes, socket_set_blocking does not work with the new socket functions, it is for the network functions, one must use set_nonblock() which to the best of my knowledge does not work under linux (or windows?) If you do a search in the list achive for sockets you will see some posts about this from me which go into more detail. Regards, Joseph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] hmm sockets (again)
Hi, I might have missed a follow up or your original message, but have you tried socket_set_blocking() ? --- Joseph Blythe <[EMAIL PROTECTED]> wrote: > Hey all, > > Just looked through the changelog for 4.0.5 and was > suprised to see that > the socket functions had not been fixed, > (set_nonblock does not seem to work under linux), I > have retried my > scripts under the new version but nothing seems to > have changed, > > For the time being I am going back to the network > and filesystem > functions which do seem to be more reliable now. > > I am a little confused though,about the following > extracted from the > changelog: > > > Fixed a compatibility problem in some file > functions (fgets, fputs, > > fread, fwrite). > > The ANSI standard says that if a file is opened in > read/write mode, > > fseek() should be called before switching from > > reading to writing and vice versa. > > How does this affect calls to a fsockopen? > > Can anybody else can confirm that set_nonblock() is > indeed broken. If it > is I will make sure that the bug is reported. > > > Regards, > > > Joseph > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > To contact the list administrators, e-mail: > [EMAIL PROTECTED] > = To find out more about me : http://www.geocities.com/mimodit My bookmarks are available @ http://mukul.free.fr -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP] hmm sockets (again)
Hey all, Just looked through the changelog for 4.0.5 and was suprised to see that the socket functions had not been fixed, (set_nonblock does not seem to work under linux), I have retried my scripts under the new version but nothing seems to have changed, For the time being I am going back to the network and filesystem functions which do seem to be more reliable now. I am a little confused though,about the following extracted from the changelog: > Fixed a compatibility problem in some file functions (fgets, fputs, > fread, fwrite). > The ANSI standard says that if a file is opened in read/write mode, > fseek() should be called before switching from > reading to writing and vice versa. How does this affect calls to a fsockopen? Can anybody else can confirm that set_nonblock() is indeed broken. If it is I will make sure that the bug is reported. Regards, Joseph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
