Re: [Firebird-net-provider] next problem

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

hi,

when you plan to release patch??? any way, are you often commiting changes
to CVS??? Is there bug fix for that record size problem???

what are CVS parameters??? On source forge i found only Firebird.NET (a .net
data provider): CVS but it looks strange... I think that it is not correct
project... So send me please server path and module name...


Your pooling is nice, but it works only while assembly is in use... when one
project ends and garbage collector decide to trash your net provider, pool
is flushed and destroyed... So if i want to create ASP.NET page i have to
link assembly to global.asax and in this situation i can use only
STAThreading... As i wrote, i have more than 20k hits to database in hour it
is more than 5 in sec... but sometimes it is more then 15hits/s... simple i
cannot use STAThreading... if i link assembly to each page, it is released
each time processing of page is done... again useless for me...
Im not forcing you to that... My be there is space for me...

i know that you are making your assembly System.Data compatible and therefor
there are that overloads. I know that they are needed, but documentation is
not clear in this way... again may be space for me...

thanx
p.

----- Original Message -----
From: "Carlos Guzmán Álvarez" <car...@te...>
To: "Pavol Starek - PSZ" <pa...@st...>; "Firebird .Net Provider"
<fir...@li...>
Sent: Monday, November 18, 2002 11:39 AM
Subject: Re: [Firebird-net-provider] next problem


> Hello:
>
>  > Can you release a patch or something??? I have now time to play with
> this assembly, so i can do lot of tests...
>
> I´m thinking on release an Alpha 4 version.
>
>  > next thing is: do you plan make it System.EnterpriseServices allowed
> it is
>  > important for performance... I plan to use your component on big
ASP.NET
>  > site (more than 20k hits a hour), but now it is unusable (pooling not
>  > working as i have to do)...
>  > My site was writen using COM+ objects in delphi. it was fast stable and
>  > scalable, but developing take to log, becouse you need to take care
about
>  > com+ logic more than your aplication logic... Net brings easy way how
to
>  > develob COM+ compliant assemblies and it is cool.
>  > I can rewrite your code to make it thread safe, but it will be hard for
>  > me... very hard... without your help... And for now im not .NET guru,
> so my
>  > code will be not very nice...
>
>
> I have no planned this, at this moment my intention is to have the
> pooling working well. Here is an example on how the pooling is working now
:
>
>      FbConnection myConnection1 = new FbConnection(GetConnectionString());
>      FbConnection myConnection2 = new FbConnection(GetConnectionString());
>      FbConnection myConnection3 = new FbConnection(GetConnectionString());
>
>      // Open two connections.
>      Console.WriteLine ("Open two connections.");
>      myConnection1.Open();
>      myConnection2.Open();
>
>      // Now there are two connections in the pool that matches the
> connection string.
>      // Return the both connections to the pool.
>      Console.WriteLine ("Return both of the connections to the pool.");
>      myConnection1.Close();
>      myConnection2.Close();
>
>      // Get a connection out of the pool.
>      Console.WriteLine ("Open a connection from the pool.");
>      myConnection1.Open();
>
>      // Get a second connection out of the pool.
>      Console.WriteLine ("Open a second connection from the pool.");
>      myConnection2.Open();
>
>      // Open a third connection.
>      Console.WriteLine ("Open a third connection.");
>      myConnection3.Open();
>
>      // Return the all connections to the pool.
>      Console.WriteLine ("Return all three connections to the pool.");
>      myConnection1.Close();
>      myConnection2.Close();
>      myConnection3.Close();
>
> What are the params of your connection string???
>
>  > Next thing is, that documentation is greate (very complex), but
> somethimes
>  > it is not good :-)  you done there lot of overloaded methods and
>  > constructors and not all are working in any way of use...
>
>
> Why?? All overloaded constructors are needed, if you see documentation
> of SqlClient, OleDb or ODBC .Net data providers you will see probably
> the same.
>
>  > Some examples are obsolete (you have there examples without
> transactions) and so... I want to help you with
>  > this project. May be i can start with documentation but you have to say
>  > exactly what to do, not only say that do something... i cannot swim,
> so you
>  > cannot throw me in to a pool...
>
>
>
> I have reviewed thew examples of:
>
> - FbConnection
> - FbDataReader
> - FbDataAdapter
> - FbCommandBuilder
> - FbCommand
>
> and i vahe it commited to the CVS.
>
>
> Best regards
> Carlos Guzmán Álvarez
> Vigo-Spain
>