[Implementation] A list of connection methods

[ColinFay]

Following #16

[Btibert3]

To build on this, it would be great if we could control the server and push/pull data (including large imports) all from the same "connection."

Thoughts would be something around defining the location of the server (environment variable, or configured option) and then:

• check server status
• start server
• stop server
• restart server
• establish a connection
• bulk import data
• bulk extract data
• keep data in list or tibble
• smaller CRUD operations
• manage constraints

[ColinFay]

For now, the con object can do some of the point you are referring to, notably check status and establish a connection.

For now the way everything is organised it is that {neo4r} will be focused on API interaction, so you just need to provide the IP adress of the server and connect. So in a sens you could use {neo4r} even if Neo4J is not on your machine. That way you can even use the package on an online Notebook, for example.

{play4j} will be used to do the orchestration you're referring to (start, stop, restart, ...), and with this package you'll need to provide the path to the neo4j bins, so Neo4J needs to be on your machine, and you may not be able to use it on an online Notebook (but in a sense, you wouldn't need to use it on an online notebook, as you don't need to manage the server on a notebook).

But in the end this is just a proposition, maybe {play4j} and {neo4r} could be one package :)

[ColinFay]

{play4j} api object will be merged into {neo4r}.

I'm keeping this issue here to keep the list, but have renamed it.