dogrocket2003 wrote:

> Forgive me if I'm talking way out of my league, and probably dont have
> a clue but... In such an extension or driver isnt the only thing
> important for it to communicate with PHP / SQL is that it have
> properly created hooks with correctly prescribed call parameters,
> whatever is inside could be delphi or even assembler code and it
> doesnt really care?
> I never coded driver or dll's just curious.
>
> I was curious about something else, is isql console reasonably fast?
> Why couldnt you make a driver that communicates via the console
> input, though not actually displaying on a screen of course. It would
> basically just be a doorway, and would allow a multitude of sql
> execution capabilitys. A long time ago in a gaming environment myself
> and a few others created a console input / output reciever... It would
> wrap requests a certain way that console would understand it, and on
> recieving end we would parse the results to work with data as we
> wished. Very minimal code would be needed I would think, just
> parsing and trapping for errors would be problem.
> I know Im nuts.. lol
>
>> Windows drivers need to be built via hte php build system for them
> to work
>> properly as plugins. Actually it's not too much of a problem since
> they SHOULD
>> build from the same code base that is used for Linux.

There is no need to reinvent the wheel dogrocket2003
http://uk.php.net/manual/en/book.ibase.php is working fine in production, but
needs updating and compiling to run with fbclient.dll directly rather than via
the legacy version on GDS32.dll

isql does not come into the equation ;)

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php