Re[4]: [PEAR-DEV] Re: go-pear. Was:Re[2]: [PEAR-DEV] XML_RPC

Hello Justin, >> >> Also go-pear can't handle correctly if internet connection is >> >> available. I've already proposed a workaround in Net_Socket and >> >> XML_RPC for this issue - gethostbyname() should be called before >> >> fsockopen() >> >> PAJ> What's the problem with go-pear working on a host with internet >> PAJ> access? >> >> Sorry, my fault. There should be phrase 'internet connection "isn\'t" >> available' or the word 'unavailable' in my post. >> >> PAJ> Do you have any other good ideas? Calling gethostbyname before >> PAJ> fsockopen is nothing than ugly and slow. >> >> fsockopen will call it anyway. You can try to call fsockopen with some >> fiction url and meditate a bit about it's error message. I'd be very >> glad if you can make a solution how to handle that error or at least >> suppress to handle it later. >> JP> *WHY*? If you don't have internet access you can't run a script which JP> needs to connect to the internet....that's how it works. Calling JP> gethostbyname will be just as slow. I miss you point probably. Do you really think one should not run go-pear if he hasn't internet connection? How about PHP distributives? Even if it so, how about to tell that user? Do you really think, that it is good for PEAR installation to crash with with standard PHP error message? If not - please, try to > call fsockopen with some fiction url first. Or try to install optional packages in PHP5 via go-pear install without internet connection to see what I want to fix. As for calling gethostbyname before fsockopen() - I don't know exactly, but how'd you think - are these DNS requests cached? How long it takes to call gethostbyname() with regard to XML-RPC parsing time? Take into account, that these two operations are called together in 1:1 ratio. No offence. Just trying to follow your logic chain. t --