Re: Re[2]: [PEAR-DEV] Re: go-pear. Was:Re[2]: [PEAR-DEV] XML_RPC
| From: | Justin Patrin | Date: | Thu, 09 Dec 2004 17:15:40 +0000 |
| Subject: | Re: Re[2]: [PEAR-DEV] Re: go-pear. Was:Re[2]: [PEAR-DEV] XML_RPC | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34963@lists.php.net to get a copy of this message | ||
On Thu, 9 Dec 2004 14:29:00 +0200, anatoly techtonik <techtonik@php.net> wrote:
> Hello Pierre-Alain,
>
> From Thursday, December 9, 2004, 2:12:21 PM, you wrote:
>
> >> Even if you place an '@'... (which I have missed in my patch),
>
> PAJ> btw, where is your patch? can you please attach it again using a
> PAJ> .txt extension only?
>
> Well, I see that none of my patches got here. =/ Now I can send you
> only cummulative. To see what had been changed follow this thread.
> Is it possible to add .patch into the list of allowed extensions?
It's not extensions, it's the content-type (at least, that's what they
say). Make sure the content-type is text/plain.
>
>
>
> >> think about the error message the user will get (I'm using PHP
> >> 4.3.9)
> >>
> >> <?php
> >> $host = 'zzzz';
> >> $fp = @fsockopen($host, 80, $errno, $errstr);
> >> if (!$fp) {
> >> print("\nconnect to '$host' failed: $errstr ($errno)\n");
> >> }
> >> ?>
> >>
> >> >connect to 'zzzz' failed: The operation completed successfully.
> >> >(0)
> >> Rather confusing if you ask me.
>
> PAJ> Makes me think about MS style messages :-).
>
> PAJ> Failed to see where it comes from (the completed part).
>
> Did you get that message?
> >> >connect to 'zzzz' failed: The operation completed successfully.
> If it so then disable @ and read PHP warning to see where does it
> come from. That's gethostbyaddr() that failed and not fsockopen()
> fsockopen() returns "i'm ok"
>
> t
> --
--
Justin Patrin