Re: [Wonder-disc] ERXObjectStoreCoordinatorPool v. ERXJDBCAdaptor's ConnectionBroker

[Mike S. <ms...@md...>]

> That's actually the exact requirement I have. an OSC per (logged in)
> user, since i have
> a limited db connections available i need pooling.
Well, there you go :)  The answer to my question ... So you really do  
have a limited set of connections available and you're going to make  
a lot of OSc's.

So one note here (that you may already know -- I just want to point  
out anyway) is that every OSC you create has its own completely  
separate set of database snapshots (i.e. backing cache for your  
EO's).  So if you fault a to-many in OSC1, and someone else faults  
the same to-many in OSC2, you will have TWO copies of that data in  
memory. So you may want to spend a little quality time doing some  
memory profiling of your app to see what exactly that really means  
(it's going to be very app-specific what the implications are).  If  
there is very little overlap in the datasets your users access, this  
might not really matter at all.  But if your users are accessing the  
same stuff all the time, you COULD end up with substantial memory usage.

ms