Thanks Peter. I was asking because of the request to support batching in neography: https://github.com/maxdemarzi/neography/issues/16
I sounds like the "normal" API is obsolete then :) It encourages non-transactional operations. I think the batch-ing should be promoted a little bit more. Check the availability and place the reservation if something is still available is pretty hard to implement without it. Not sure if batching supports conditional operations though. Does it? Is there anything that would be impossible/slow etc to do with batching? I mean, there must be some drawbacks :) Cheers. On 01/12/2011, at 6:08 PM, Peter Neubauer wrote: > Dmytri, > sounds like an interesting plan! I don't think there is anything > directly that I can see, except a bug, > https://github.com/neo4j/community/issues/113 with "\\" which you > might watch our for, reported by Josh Adell. > > Let us know how it works out! > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > brew install neo4j && neo4j start > heroku addons:add neo4j > > > > On Thu, Dec 1, 2011 at 5:53 AM, Dmytrii Nagirniak <dna...@gmail.com> wrote: >> Hi, >> >> I wonder what the disadvantages would be if every request to the server >> would always be a batch (even for simple GETs)? >> >> This would make it easier to use the API from the application. >> >> How bad is this idea? >> >> Cheers, >> Dima >> http://www.ApproachE.com >> >> >> >> >> _______________________________________________ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
