To toss my two cents in, I had been thinking about moving my REST library to
use only batches for all CRUID operations.  I've been putting it off, and I
will probably drop the idea for now based on Jake's response.


Jacob Hansson-2 wrote
> 
> 1. There are limits to how large the results can be from a batch API
> call...
> 
> 2. ...We have lots of ideas for how we
> can improve the current REST API (add full transactional support,
> massively
> improve throughput and latency)...
> 

Having real transactions via the REST API (a bit of an oxymoron?) would be
most welcome.

-- Josh

PS, has anyone else used the acronym CRUID (Create Read Update Index Delete)
to describe Neo4j operations? My other attempt was "ICRUD" but that sounds
like the stuff you rub out of your eyes when you wake up in the morning.

--
View this message in context: 
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-API-always-batch-tp3550568p3551739.html
Sent from the Neo4j Community Discussions mailing list archive at Nabble.com.
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to