Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote C# client [moved] #68

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Remote C# client [moved] #68

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 68 moved from a Google Code project.
Added by 2010-07-20T23:34:35.000Z by j...@supporters.dk.
Please review that bug for more context and additional comments, but update this bug.
Closed (Invalid).

Original labels: Type-Enhancement, Priority-Low

Original description

Please consider developing a separate client library (preferably C#) isolated from the main project, that make use of the binary protocol instead of the REST API, to establish a connection to a remote database. 

The REST API performance seems quite slow (it sometimes take about a second to get a node via REST, whereas Neo4j REST API takes about 40ms - note: it might be the authentication). Anyway, a connection through a binary protocol would be better than REST.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant