- [EMAIL PROTECTED]% (Michael Sisolak):
> This is exactly the error I am seeing: if I load an ASP page in a
> thread that has processed PHP pages I get the 270 error (reported as
> "Error -2147417842 (0x8001010e)"). I moved the CoInitilize call to
In regard to the latest thread about error messag
- [EMAIL PROTECTED]% (Chris Shiflett):
> I assume it is because such an extension would somehow be required to be
> covered under the GPL as well, but I don't understand that. Shouldn't it
> be possible for the PHP extension's code to be licensed any license and
> simply use a GPL library? The e
- [EMAIL PROTECTED]% (Jim Mercer):
>> It will be yet another safe_mode like feature. i.e.
>> it isn't secure as it sounds. Users with a little knowledge
>> can access backend with socket function. Therefore, I agree
>> with Ilia's opinion.
> the concept here is security, and i recognize that part
- [EMAIL PROTECTED]% (Marcus Börger):
> But according to your example i think google prohibts accessing their
> search engine etc. through software...
A bit off-topic; but google has its own "Web API" for developers
wanting to access google-results:
http://www.google.com/apis/
--
mats
--
PH
on issue (maybe it should be noted that its
just meant for pages served through a webserver) or should this be
considered a bug?
--
Mats Lindh - [EMAIL PROTECTED]
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
- [EMAIL PROTECTED]% (Brian Foddy):
> So they download both and start building. What do they get?
> Core dump. Usually before people will start opening trouble
[cut]
> with these two latest releases. "Experimental, not for production"
> just doesn't cut it. Not when we KNOW there is a definat
- [EMAIL PROTECTED]% (James E. Flemer):
> This patch I think will catch all cases, unless there is
> some way that mysql can escape characters (\x44 or
> something).
As far as i can see, this patch will disable all LOAD DATA-cases, this
will however disable a feature in MySQL for loading files th
