Hi all! Today I committed my latest Neo pet project to laboratory in the repository. It is something that I hope will be useful enough to one day become a component. I call it RemoteNeo.
RemoteNeo is a NeoService implementation that does not implement any persistence of its own. Instead it uses a transportation layer to communicate with another Neo instance. The other Neo instance could be running in the same JVM but RemoteNeo becomes a lot more interesting when you have the persisting Neo instance running in a separate process, or even another computer (halfway across the Internet?). See also ticket #63: https://trac.neo4j.org/ticket/63 I got the idea to write RemoteNeo from a discussion about connecting to a running Neo instance in Neoclipse (see ticket #42: https://trac.neo4j.org/ticket/42). To me it makes a lot more sense to have a remote layer for Neo that implements the Neo API, instead of doing specific implementations for every separate component that needs remote connection. And IMHO this is the major benefit of RemoteNeo, that it implements the Neo API. This means that you transparently can drop in RemoteNeo as areplacement for EmbeddedNeo. RemoteNeo is in a very early state, pre-alpha or proof of concept even. As such there is a lot of work still to be done. I would like help from you, my fellow community members in this process. The issues we have to work on at the moment are: 1. Write more tests! 2. Evaluation of the communication layer API (org.neo4j.remote.RemoteConnection). 3. Performance tuning and caching. If you would like to have a look at RemoteNeo you can get the source from https://svn.neo4j.org/laboratory/users/tobias/RemoteNeo/. Please comment and discuss! Happy hacking! - -- Tobias Ivarsson <[EMAIL PROTECTED]> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
