Re: Re: the body of the response
| From: | CC Zona | Date: | Mon, 16 Jul 2001 22:40:05 +0000 |
| Subject: | Re: Re: the body of the response | ||
| References: | 1 2 3 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-10481@lists.php.net to get a copy of this message | ||
In article <00c801c10e3f$758ba8a0$b943500c@zeospantera>,
mrsql.php@worldnet.att.net (Ken Sommers) wrote:
> are you saying that i can grab the output of your echo() statements in YOUR
> PHP script by Fopen()ing your URL
Yes, you can use it that way.
> IF so,, is this done much?
It's done. I can't quantify how often. But it's not considered usual or
unorthodox, if that's what you're asking.
> or are there easier more stable less error-prone
> ways to access remote databases?
A) If you're trying to access a remote DBMS with fopen(), then the
probability is very high that's your whole strategy is bass-ackwards. So
if that's what's behind these questions, your confusion is
understandable--time to do a major re-think (and/or, as Ken has already
suggested, spend more time with a PHP manual).
B) What makes you think fopen is unstable or error-prone? I'd expect any
connection to a remote server to have a higher risk of errors than a local
connection, but you seem to believe that fopen() itself introduces new
opportunities for errors above-and-beyond the remote connection itself.
That I would not expect to be the case.
--
CC