Watch, Follow, &
Connect with Us

Please visit our new home
community.embarcadero.com.

Public Report
Report From: InterBase/Interfaces    [ Add a report in this area ]  
Report #:  1313   Status: Reported
Request for better middle tier support
Project:  InterBase Build #:  1.0.0.74
Version:    6.5 Submitted By:   John Small
Report Type:  Suggestion / Enhancement Request Date Reported:  5/20/2002 4:46:41 AM
Severity:    Commonly encountered problem Last Updated: 5/2/2003 12:58:35 PM
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
2.00 out of 5
Total Votes: None
Description
To make better use of Interbase as the back end database for a n N-tier system we need proper support for connection pooling and multithreading.  

Currently when writing a Datasnap system using COM+ the fact that there is no connection pooling means that many connections can be kept open even though they are not in use. The alternative is to open and close connections for each call which has a terrible impact on performance.

Also I've got wierd problems with the said Datasnap server under COM+ which I assume must be due to threading issues


Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments

Craig Stuntz at 5/22/2002 12:06:00 PM -
It sounds to me like what you really want is a .NET managed provider with support for COM+ transactions.  There is nothing in IB presently which prevents you from pooling connections (indeed, IBX already includes a component for this) and IB is thread-safe when you play by it's rules, but what you're asking for is direct support for the COM+ (soon to be known as ADO.NET) interface.

Server Response from: ETNACODE01