On Thu, Oct 6, 2011 at 1:57 PM, Peter Neubauer < [email protected]> wrote:
> Yes Javier, > that would be great! Do you think you could open an issue and provide > some details on how to go about it? > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > http://www.neo4j.org - Your high performance graph database. > http://startupbootcamp.org/ - Öresund - Innovation happens HERE. > http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. > > > > On Wed, Oct 5, 2011 at 5:15 PM, Javier de la Rosa <[email protected]> > wrote: > > On Wed, Oct 5, 2011 at 07:48, Jacob Hansson > > <[email protected]> wrote: > >> there is now a first stable release of the new "neo4j-embedded" > >> python package available from PyPi. > > > > This news is really great! And I'm very glad to see that some methods > > are seemed to the neo4j-rest-client [1]. Is there any chance to find > > some day from neo4j import restgraphdatabase and to make both > > API's totally equal? > > > > Thank you very much for all the work involved. > > Regards! > > > > > > > > [1] https://github.com/versae/neo4j-rest-client > > > > -- > > Javier de la Rosa > > http://versae.es > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > Javier, it would be really awesome to combine the two, or at least make sure the APIs are completely compatible. I'm hesitant to bundle them together, because the REST client is pure python, and can keep a very small footprint. The embedded package, on the other hand, bundles the full Neo4j distribution, and so it's a full 10MB large. In most settings, this won't matter much, but it still feels unnecessary to force people who just want the REST client to include the full DB distribution in their projects. Architecture-wise, perhaps we can have a common front for them, that can then be powered either by the embedded implementation, or by the REST client, and then use something like the db path to determine which one to use: from neo4j import GraphDatabase embeddeddb = GraphDatabase('/home/data') serverdb = GraphDatabase('http://localhost:7474') There is one major hurdle we need to get past first, we need to implement transaction support in the REST API that is feature-compatible with the embedded transaction API. When that is in place, the REST client will be able to behave exactly like the embedded client, and we can combine them. /Jake -- Jacob Hansson Phone: +46 (0) 763503395 Twitter: @jakewins _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
