Support Bolt for Neo4j 3.0

Right, so it’s time to consider the Bolt issue - my general feelings on this is that ideally you shouldn’t have to change your codebase - i.e. if you use IGraphClient then that should still apply now.

Ideally I’m thinking something like:

var client = new BoltGraphClient(new Uri("bolt://localhost:7687"));
client.Connect();

client.Cypher.Match("n").Return(n => n.As<Movie>()).Results;

i.e. only change the new GraphClient to new BoltGraphClient.

As to how realistic this is - that’s a ‘need to investigate’ type issue.

Other questions go along with this:

1. Should the Bolt bit be released as a separate nuget package? i.e. Neo4jClient.Bolt - I quite like this idea - it means that the current project can stay as it is - i.e. keep gremlin / rest support for those who use it (which I’d be interested to know) and if you want to use 3.0 over Bolt, you add the other package.
2. In terms of the Bolt implementation - one problem with IGraphClient is the bucketload of backage - in practice - you’d probably only want .Connect(), .Cypher etc, would it be worth having an IBoltGraphClient - which obviously would require code changes for existing projects, but would make the intellisense nicer.

This is a substantial change, a major version increment, so whilst we don’t want to go crazy - some breaking changes are (I think) acceptable.

Other points please chip in here, this is a question type issue - looking for feedback, ideas, etc

[cskardon]

Not quite - Neo4jClient does support Neo4j 3.0 - what it doesn’t support is the bolt protocol. The conversion/addition plan is to make Neo4jClient support bolt, but from a user point of view - I only want one line to change, so instead of: new GraphClient(new Uri("http://localhost.:7474/db/data")), I want it to read new GraphClient(new Uri("bolt://localhost/")) - everything else should stay the same.

[cskardon]

Good call