Hi Lester,

Lester Caine ha scritto:

> I have always worked on the principle that I only want one copy of the client
> in use, so PHP, flamerobin and the legacy IBO applications will share that.
> What is being proposed is that PHP will have it's own client in it's own
> directory, and that will not cause problems with other applications accessing
> the same databases via a different copy of the client probably compiled with a
> different version of VC.
>
>

Ok, I really don't understand what is the "support" part of the PHP
querelle.
What happens? PHP support says that he needs fbclient.dll to be compiled
(or already compiled) for VC6 (to be compatible with Apache AFAIU) and
for VC9 (for other Web servers, i.e. IIS) otherways they cannot
include/develop/maintain PHP firebird client libraries (ext/interbase)
in distribution PHP 5.3 and 6.0 (for Windows).
IMHO this belongs to PHP and (perhaps) devel lists.
Anyway, I'm not really convinced we have unveiled and explained all
points with PHP support team, because, as you pointed out, they AFAIU
tend to distribute an additional copy of client lib (fbclient.dll) in
PHP for Windows, ignoring that having possibly installed FB server on
the same Web server, ther is already another (differet!) copy somewhere
in the same system.
Which copy goes on system dir to serve, say, Flamerobin, legacy IBO
application, and so on? Last wins?
Other question: localhost connection through first client lib conflicts
with local connection through the other lib?
i.e.: you can have web server connecting through local and other
programs using localhost: this can solve?

Ciao.
Mimmo.