Re: Database resultset managing best practices

 CSM> On a related note.....although not space-based between client and
 CSM> server, Athena (http://athena.dev.java.net) does translate from
 CSM> datasets (not just java.sql.ResultSet) into a serialized table based
 CSM> data model - it also handles transferring large resultsets in chunks
 CSM> thus staggering the cost of the remote calls. In a space based
 CSM> implementation, I would consider having some form of chunk identifier
 CSM> in the results, and splitting large resultsets into multiple entries,
 CSM> so that you can read the first chunk as other chunks are being placed
 CSM> into the space - this opens many concepts such as parallel queries,
 CSM> etc.

A very interesting note. Actually I've resolved with RowSets, but it
effectively  seems that  this approach is suitable if data are small. If
necessary, I'll try to do a view to Athena, or even a custom solution based
on your "chunk entry" idea.

Thanks

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html