Re: Database resultset managing best practices

Andrea Angeloni wrote:
> Thanks everyone for the suggests.
>
> GW> Storing large objects into Javaspaces as a temporary exchange of data
> GW> interface, is possible, but unless you have lots of queries and lots of
> GW> work for each query where you want to distribute the load, the use of
> GW> Javaspaces might not be a good match.
>
> Yes, but I'm doing a theoretical work, it's a proof rather a real word
> application (where performances and other non-funtional aspects may be
> critical).
> I'll try to compare this solution with conventional DB apps.
>
> By the way, is there somewhere where I can find a comparison between a
> "space-based db platform" and an ordinary n-tier architecture db platform?
> N.B using JavaSpaces as a middleware, not as a persistence layer, as a "db"
> itself).

You might also find my http://griddle.dev.java.net project interesting from the
perspective that it has an executor and non-equals matching.  These things can
provide for a different construction of a space-like application.  I've not been
able to use griddle for it's designed goal yet.  It's an evaluation technology
more than a production environment.  But, if you're doing some research in this
area, I'd appreciate having some feedback on it.

Gregg Wonderly

===========================================================================
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