Hi, I've just spent a few evenings writing a connection pool for OrientGraph instances <https://github.com/skwidge/OdbResource/releases>. It has become clear that it is never going to be very good if it only sits on the outside of the public API.
Essentially I want to add a feature to the OrientDB authentication model. At the moment you have to pass in your credentials when you construct an OrientGraph instance, and it uses the same credentials for the lifetime of that instance. I would like to be able to cheaply associate a new set of credentials with an existing OrientGraph instance to facilitate connection pooling. This could allow developers to leverage the record level security model for all users of a web application if it were backed by an OrientDB database. I've written up a discussion of the ideas <http://skwidge.github.io/OdbResource/doc/whitepaper.html> as well as the proof of concept connection pool <https://github.com/skwidge/OdbResource/releases>. I would be interested to know, do other people see value in this idea? I would love to try to implement a patch to allow this, but I'm not sure yet if it would get support from Orient Technologies or the community. CHrs, Bruce -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
