ay 11, 2011 at 8:01 AM, Rick Bullotta
> > wrote:
> >
> >> I think you have to still do it over HTTP *in addition* to any other
> >> transport, if for no other reason than the ubiquity of HTTP-capable
> client
> >> applications/platforms/languages. That said, I&#x
ot;time to live".
>>
>> -Original Message-----
>> From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org]
>> On Behalf Of Jacob Hansson
>> Sent: Wednesday, May 11, 2011 10:58 AM
>> To: Neo4j user discussions
>> Subject: Re: [Neo
mailto:user-boun...@lists.neo4j.org]
> On Behalf Of Jacob Hansson
> Sent: Wednesday, May 11, 2011 10:58 AM
> To: Neo4j user discussions
> Subject: Re: [Neo4j] REST API (optimistic or transactional) concurrency?
>
> We started discussing how an implementation would look, but bumped into
me to live".
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Jacob Hansson
Sent: Wednesday, May 11, 2011 10:58 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] REST API (optimistic or transactional) concurrency?
We started discussing how an
We started discussing how an implementation would look, but bumped into
problems.
The plan was to look at potentially adding a restful transaction API,
something like "create a transaction context resource via a POST, and then
work with the database "via" that context resource, commiting/aborting
Just wanted to ask: how'd the lab day go last Friday? Any updates on this?
=)
Cheers,
Aseem
On Thu, May 5, 2011 at 7:42 AM, Mattias Persson
wrote:
> 2011/5/5 Aseem Kishore
>
> > Yes, great points.
> >
> > I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure
> > Table
> > Stora
2011/5/5 Aseem Kishore
> Yes, great points.
>
> I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure
> Table
> Storage, and for what it's worth, I thought they solved this problem very
> elegantly. That API is entirely REST-based, and they use HTTP If-Match /
> If-Modified-Since
Yes, great points.
I've worked a good deal with Microsoft's cloud NoSQL DB, Windows Azure Table
Storage, and for what it's worth, I thought they solved this problem very
elegantly. That API is entirely REST-based, and they use HTTP If-Match /
If-Modified-Since headers to achieve conditional reques
Assem,
I agree. The problem is not the database API IMHO, but the mismatching
semantics of HTTP REST and transactional DB APIs, and the balancing of
shoving over work to the database server via server side processing
scripting or plugins and client side operations via HTTP. Let's see if
we can come
Thanks Peter. Looking forward to seeing what you guys come up with!
Dima, thanks for the tip. It would be nice to not to have to write a custom
plugin for what's arguably a pretty fundamental need from database APIs. =)
Aseem
On Wed, May 4, 2011 at 2:05 PM, Peter Neubauer <
peter.neuba...@neotec
Guys,
Friday is labday, so we there are tentative plans to sketch on some
transactional semantics in the REST API and circle back to the list on
that. Let's see how it goes!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http:/
You should implement your own plugin/component on the standalone neo4j
server and expose you own API that makes batch operations.
Regards,
Dima Gutzeit.
Sent from my iPhone
On 4 במאי 2011, at 21:56, Aseem Kishore wrote:
> Re-sending in the hopes that someone has answers to or thoughts on this.
Re-sending in the hopes that someone has answers to or thoughts on this. =)
Aseem
On Mon, May 2, 2011 at 4:16 PM, Aseem Kishore wrote:
> Hi there,
>
> If we're using Neo4j purely over REST, do we have any means to protect
> against concurrency? The REST API appears to expose neither transactions
13 matches
Mail list logo
