Re: new EOObjectStoreCoordinator and closing database connection afterwards
Re: new EOObjectStoreCoordinator and closing database connection afterwards
- Subject: Re: new EOObjectStoreCoordinator and closing database connection afterwards
- From: Chuck Hill <email@hidden>
- Date: Tue, 1 Jul 2008 22:00:08 -0700
On Jul 1, 2008, at 9:41 PM, Mike Schrag wrote:
I would look at Wonder source and see what trickery is being used
to implement this fix.
I don't think we close ... The OSC pool in Wonder is designed to
be round-robin'ed across requests and never needs to close.
I recall a discussion from a while ago that actually getting EOF to
close the connection is difficult / impossible. I have never
needed to (see Mike's comment above), so I have never looked into it.
Maybe you're referring to the jdbc2Info connection? It's not
impossible, but it is very tricky. I don't THINK this is his
problem here, though.
Yeah, that is probably what I am remembering. Mike's very tricky ==
impossible for most people. ;-)
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden