firebird-net-provider

[Firebird-net-provider] Firebird Services API implementation.

[Carlos G. A. <car...@te...>]

Hello:


I'm implementing in the C# GDS implementation methods for handle 
Services API of Firebird, now i want to know people thoughts on some 
questions:

	1. It's interesting or not to make a set or clasess wrapping the 
Services API ??

	2. If asnwer to the first question is Yes, how we can implement it:
	2.1 As a single public class called FbServices and let people to wrap it.

	2.2 Make a set of classes wrapping the Services funcionaluty, for 
example FbBackup, FbRestore, FbXXXXX, and here we need to think if we 
want to wrap all the funcionaly or only some things and how to expose 
the funcionality ( like Services API constants ).

	2.3 Other ??


My answers are:

	1. Yes.

	2. I think method 2.2 it's better.



-- 
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

"No tengo dones especiales.Sólo soy apasionadamente curioso"
Albert Einstein, científico.

[Firebird-net-provider] Firebird Services API implementation.

[Christopher W. <chr...@ad...>]

> Hello:
>
>
> I'm implementing in the C# GDS implementation methods for handle
> Services API of Firebird, now i want to know people thoughts on some
> questions:
>
> 1. It's interesting or not to make a set or clasess wrapping the
> Services API ??
>
> 2. If asnwer to the first question is Yes, how we can implement it:
> 2.1 As a single public class called FbServices and let people to wrap
it.
>
> 2.2 Make a set of classes wrapping the Services funcionaluty, for
> example FbBackup, FbRestore, FbXXXXX, and here we need to think if we
> want to wrap all the funcionaly or only some things and how to expose
> the funcionality ( like Services API constants ).
>
> 2.3 Other ??
>
>
> My answers are:
>
> 1. Yes.

Also Agree.

> 2. I think method 2.2 it's better.

Also Agree.

I also think having 2 assemblies would provide the option of installing
only the
needed set.

I also want to say thank you for this great software library and your
quick responses to problems.  I am planning on using it
for my own product!

Regards,


Chris Whelan

Re: [Firebird-net-provider] Firebird Services API implementation.

[Carlos G. A. <car...@te...>]

Hello:

> I also want to say thank you for this great software library and your 
> quick responses to problems.  I am planning on using it
> for my own product!

Thanks.




-- 
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

"No tengo dones especiales.Sólo soy apasionadamente curioso"
Albert Einstein, científico.

Re: [Firebird-net-provider] Firebird Services API implementation.

[Alessandro P. <pet...@in...>]

"Carlos Guzman Alvarez" <car...@te...> wrote in message
news:3EB...@te......
> Hello:
>
>
> I'm implementing in the C# GDS implementation methods for handle
> Services API of Firebird, now i want to know people thoughts on some
> questions:
>
> 1. It's interesting or not to make a set or clasess wrapping the
> Services API ??
>
> 2. If asnwer to the first question is Yes, how we can implement it:
> 2.1 As a single public class called FbServices and let people to wrap it.
>
> 2.2 Make a set of classes wrapping the Services funcionaluty, for
> example FbBackup, FbRestore, FbXXXXX, and here we need to think if we
> want to wrap all the funcionaly or only some things and how to expose
> the funcionality ( like Services API constants ).
>
> 2.3 Other ??
>
>
> My answers are:
>
> 1. Yes.

Agree.

> 2. I think method 2.2 it's better.

Agree.

Are you going to provide 2 different assemblies or only 1?
I think having 2 assemblies would provide the option of installing only the
needed set.

Thanks for this wonderful piece of software. It works very well, I'm going
to use it in a large project.

Regards,
Alessandro Petrelli.

Re: [Firebird-net-provider] Firebird Services API implementation.

[Carlos G. A. <car...@te...>]

Hello:

> Are you going to provide 2 different assemblies or only 1?
> I think having 2 assemblies would provide the option of installing only the
> needed set.

My first idea is to release only one assembly but depending on resulting 
Services class hierarchy can be better to provide two assemblys.

> Thanks for this wonderful piece of software. It works very well, I'm going
> to use it in a large project.

Thanks to you :)



-- 
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

"No tengo dones especiales.Sólo soy apasionadamente curioso"
Albert Einstein, científico.

Re: [Firebird-net-provider] Firebird Services API implementation.

[Pavol S. <pa...@st...>]

Hi,

its better to do for each function own class, becouse if you want to 
implement FbPermissions you will need this...

p.

Re: [Firebird-net-provider] Firebird Services API implementation.

[Carlos G. A. <car...@te...>]

Hello:

> its better to do for each function own class, becouse if you want to 
> implement FbPermissions you will need this...

Thanks


-- 
Un saludo

Carlos Guzmán Álvarez
Vigo-España

"No tengo dones especiales.Sólo soy apasionadamente curioso"
Albert Einstein, científico.