Re: [Firebird-devel] Porting Firebird

[Tagangout, A. <Abd...@me...>]

Hi Dmitry,
many thanks for your answere.

i find the location where the communication with the TCP-Driver will be solved.
1- When i try only a attach-Command to an Firebird Server from a client, where will be the attach-String saved to be send to the TCP-Driver?
2- Is there any Documentation for this issue? How the isql Commands are Managed in a Packet, that would be transmitted to the TCP-Driver?

Many thanks
Abdo


MEP Kutsch GmbH & Co. KG
Flaßkuhle 1
58452 Witten
Tel. : 02302 28262-41
Fax.: 02302 28262-99

mailto:abd...@me...

http://www.mep.de

-----Ursprüngliche Nachricht-----
Von: Dimitry Sibiryakov [mailto:sd...@ib...] 
Gesendet: Mittwoch, 29. September 2010 12:36
An: For discussion among Firebird Developers
Betreff: Re: [Firebird-devel] Porting Firebird

29.09.2010 12:28, Tagangout, Abderrahim wrote:
> Can you make only one or two changes on this file so i can folow them? Or tell me where should i make this changes and to give the Y-valve only the remote provider?

   It is done automatically if macro SUPERCLIENT is defined during build. This macro is defined in Makefile.libfbclient.

> sorry for this banal question, but what does mean remote-provider?

   This is Firebird module which provides ability to work with remote Firebird server. 
Mostly placed in src/remote dir.

-- 
   SY, SD.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel