firebird-net-provider

[Firebird-net-provider] New assembly distribution for next version (1.6 or 2.0)

[<car...@te...>]

Hello:

With the need of give support to the embedded server i'm thinking in 
redistribute the classes in some assemblys, for the next version, 1.6 or 
2.0 i have not decided it yet :), my first thought is :

(1) FirebirdSql.Data.Firebird.dll

	With ADO.NET classes.

(2) FirebirdSql.Data.Common.dll

	With common classes for all GDS implementations

(3) FirebirdSql.Data.Gds.dll

	Witch classes for the native C# GDS implementation.

(4) FirebirdSql.Data.FbClient.dll

	Witch classes for the PInvoke GDS implementation.



Opinions are wellcome!!! :D


--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

Re: [Firebird-net-provider] New assembly distribution for next version (1.6 or 2.0)

[Wendell W. <wjw...@ho...>]

Hi,

"Carlos Guzmán Álvarez"  wrote:
> With the need of give support to the embedded server i'm thinking in
> redistribute the classes in some assemblys, for the next version, 1.6 or
> 2.0 i have not decided it yet :), my first thought is :
>

I have been reading some posts on the Firebird-Architect list from 10/2003
regarding 'External "procedural engine" modules' and possible future
directions for hosting the Java VM as a Stored Procedure execution
environment.

Is anyone else interested in hosting the .NET Runtime as an environment for
Stored Procedures and Triggers?  Has anyone considered how much of the
existing C# code can be reused for such a project?  I assume that part of it
will have to be a managed C++ wrapper of some sort that hosts the runtime in
the FB engine, but I have not looked into the details yet.  I expect it will
be a Win specific build of FB (perhaps post FB 1.5 after it is RC is done)
since I'm not sure if Mono:: is ready to be hosted like this yet on linux.
I'm relatively new to Firebird and have not examined its internal design a
lot, but I am not new to programming and could brush up my C++ skills of old
if time allowed.

Is this the right time to lay the groundwork for this design as you decide
how to arrange the assemblies and namespaces?  Or am I getting way ahead of
myself?

Sincerely,
Wendell Wilkie

Re: [Firebird-net-provider] New assembly distribution for next version (1.6 or 2.0)

[<car...@te...>]

Hello:

> Is this the right time to lay the groundwork for this design as you decide
> how to arrange the assemblies and namespaces?  Or am I getting way ahead of
> myself?

I think this would be of interest in the future, but at this moment, as 
i know, there are nothing decided on if this is really going to be 
implemented in the engine and if it's going to be made, nothing known 
about how it's going to be done, or there are anything decided yet ??







--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

Re: [Firebird-net-provider] New assembly distribution for next version (1.6 or 2.0)

[<car...@te...>]

Hello:

> (4) FirebirdSql.Data.FbClient.dll

As Pierre Arnaud has suggested to me i'm going to change this assembly 
name to:

	FirebirdSql.Data.Embedded.dll

In first place i was thinking on use it for the fbclient.dll too but as 
the primary goal is to get support for the embedded server second name 
is more correct.

For know which client assembly to use i will use a "ServerType" 
parameter in the connection string:

* ServerType = 0

	For Super Server and Classic Server using the pure C# GDS.

* ServerType = 1

	For Embedded server using the PInvoke GDS.


As always opinions are very welcome.



--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain