Jamie,

Thanks for writing. [Awful site, BTW, for making you register, then
registration doesn't work, pushing pubs down your throat... Thank
goodness I have GMail to filter out all the spam I'll no doubt get
from the site's registration!]

So I see the differences as:

1. With .NET you have a connection string in each piece of code using
the pool instead of instantiating a connection to an existing pool.
2. If you fail to leave at least 1 .NET connection open, the pool goes
away, and needs to be recreated the next time it is needed, where a ds
would stay available for fast connectivity-even on the first
connection to the pool.
3. You need to have precisely the same connection string in the app,
where a reference to a ds class is all that is needed for a java app
server.

No biggie, as long as the back-end, low level functionality is the
same. I was really starting to worry, thinking that a lack of
effective db pooling was why the larger systems use Java. I have
enjoyed writing VB.NET clients for years, but only now have started
with the server. I originally wanted a VB.NET client with a J2EE back
end, but getting web services to run properly was a nightmare. I spent
months in EJB3 code trying to make things work, and they never quite
did. A week with VB.NET and WCF, and I feel like I can actually move
on to hte actual programming (business logic).

A friend once called this extra work "shaving the Yak". He was
referring to all the time we figure out HOW to get our code to work,
instead of actually writing the code. Getting web services to work as
needed is a great example. I'm not in the business of writing web
services-far from it. I'm in the business of writing business logic.
The beauty of EJB3/J2EE was that the container took care of all the
messy bits, leaving you to just your logic-the actual application.

I'm hoping .NET/WCF will prove an easier way to get where I need to
be. Thanks for all the help!

pat
:)

On Oct 22, 4:12 am, Jamie Fraser <[email protected]> wrote:
> .Net supports Connection Pooling just as Java does.

Reply via email to