Re: Zero-copy persistence with Struts?

[Eddie Bush]

No, you're right Jacob. It would, in fact, have to do a copy. I don't, quite frankly, know why I misrepresented it. I think it's still more minimalistic than OJB though - so the original person asking may yet prefer it. I certainly would rather see a person use CRS than keeping ResultSets open (and Connections and ... ) ... what a headache that'd be. Can you imagine all the hoops he'd have to jump through to *try* (because I don't think he'd always succeed) and make sure his connections etc always got closed? Insane!

Hookom, Jacob John wrote:

I guess I'm lost as to why CachedRowSet is a zero copy?  The source code for the basicPortal's still copies all the data into another, internal collection.  Isn't that copying the data or did I miss the definition of zero copy?  With OJB, objects are placed in a cache, so if you are querying the db, and a row is returned as an object, it's first fetched from the cache-- zero copy.  With each request with a CachedRowSet, aren't you instantating just as many objects each time, granted you aren't wrapping the columns in an object, but you are still wrapping them in something like an Object[] or a Map (gasp).  Even if you were to re-use the CachedRowSet as part of an action at the application scope, you would be needing to load all the data for every user to be able to filter over as you push it to the jsp.  Please catch me if I'm mistaken.

Regards,
Jacob

--
Eddie Bush




--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>