On Tue, Nov 1, 2011 at 5:37 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Well,
I think that Cypher is not yes taking into account Uniqueness, or is
it Andres? Otherwise, most of the normal traversals are covered.
To keep things consistent and give people a way of doing fine
I vote not dropped, as there are lots of non-java developers out there which
would want to use REST server dynamically.
That was the reason why we wrote the ruby-script-extension support.
Michael
Am 02.11.2011 um 10:08 schrieb Jacob Hansson:
On Tue, Nov 1, 2011 at 5:37 PM, Peter Neubauer
On Wed, Nov 2, 2011 at 10:20 AM, Michael Hunger
michael.hun...@neotechnology.com wrote:
I vote not dropped, as there are lots of non-java developers out there
which would want to use REST server dynamically.
I am completely open to the notion that I am wrong here. But I want us to
have
custom use-cases like the ones implemented by our customers with plugins /
extensions
and in the case of the ruby script extensions a way I'd like to promote to talk
to the server that is
1) create you own RESTful endpoints that are focused on a protocol speaking
your domain and not nodes +
On Wed, Nov 2, 2011 at 11:11 AM, Michael Hunger
michael.hun...@neotechnology.com wrote:
custom use-cases like the ones implemented by our customers with plugins /
extensions
and in the case of the ruby script extensions a way I'd like to promote to
talk to the server that is
1) create you
On Wed, Nov 2, 2011 at 11:56 AM, Jacob Hansson
jacob.hans...@neotechnology.com wrote:
On Wed, Nov 2, 2011 at 11:11 AM, Michael Hunger
michael.hun...@neotechnology.com wrote:
* custom traversals with complicated callbacks
This is really what my original question to Peter was about -
On Wed, Nov 2, 2011 at 12:34 PM, Andres Taylor
andres.tay...@neotechnology.com wrote:
On Wed, Nov 2, 2011 at 11:56 AM, Jacob Hansson
jacob.hans...@neotechnology.com wrote:
On Wed, Nov 2, 2011 at 11:11 AM, Michael Hunger
michael.hun...@neotechnology.com wrote:
* custom traversals
Mmh,
this thread is just about deprecating the travers() section of the
REST API, not take away general scripting form the server. I have not
seen one single case where people have exploited the JavaScript
exposure in the return/stop evaluators to do anything like you say
Michael.
Extensions and
On Wed, Nov 2, 2011 at 3:44 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Mmh,
this thread is just about deprecating the travers() section of the
REST API, not take away general scripting form the server. I have not
seen one single case where people have exploited the JavaScript
Yes.
This thread is about ONLY the traverse-Endpoint not scripting in general.
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
Hi,
We use the REST traversal API extensively. One of our core use cases is to
find all paths between two nodes. We are a .Net shop so we rely on the
REST API, and are currently using a .Net neo4j library from about 18 months
ago that we have customized to our needs.
I have seen other recent
As I said it is still used in the rest-graphdb-client which comes as a
drop-in-replacement for the core-api.
This functionality would go missing then.
Same goes for lot of stuff that for instance neography does with the REST
server to offer a quite fluent way of traversing the graph.
See
Ok,
then let's shelf this until further notice, and revise it when we have
done some more extensive work on the server and fast protocol stack.
Thanks for all input, good that you speak up!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
It would be interesting to rephrase the question like this:
Are there any use cases that the REST traversal API covers, that we
currently cannot replicate in Cypher or Gremlin?
On Sun, Oct 30, 2011 at 2:45 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Well,
Andres has been
Also,
there is another possibility: We are exposing a ECMA script execution
engine via the Traverse enpoints. Instead of trying to shoehorn the
traversal API into REST calls and then anyway executing script
snippets, Why not exposing a JavaScript plugin along exactly the same
lines as the Groovy
You, something like Neo4js https://github.com/neo4j/neo4js? We've had
that since forever. Or do you mean something different?
Andrés
On Tue, Nov 1, 2011 at 5:06 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Also,
there is another possibility: We are exposing a ECMA script
Nope,
I mean a server side script execution (which we already are doing in
http://docs.neo4j.org/chunked/snapshot/rest-api-traverse.html) to
execute traversal API code on the server. Neo4js is a client driver.
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone
On Tue, Nov 1, 2011 at 5:22 PM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Nope,
I mean a server side script execution (which we already are doing in
http://docs.neo4j.org/chunked/snapshot/rest-api-traverse.html) to
execute traversal API code on the server. Neo4js is a client
Well,
I think that Cypher is not yes taking into account Uniqueness, or is
it Andres? Otherwise, most of the normal traversals are covered.
To keep things consistent and give people a way of doing fine grained
traversals, I would then suggest to document all the existing examples
using Cypher or
Well,
Andres has been putting the first algo into cypher and we are thinking of
exposing them there so thru can be used as path functions in an expression.
However, that will be step 2. WDYT?
On Oct 29, 2011 6:47 PM, maxdemarzi maxdema...@gmail.com wrote:
I think the traversal rest api is fine
I think the traversal rest api is fine for my purposes, but if cypher is
where we want to go long term, then we need to deprecate it in 1.6 and drop
it in 1.7.
This gives us some time to update our libraries and for cypher to settle
down.
Are you guys thinking of getting rid of the rest built in
I think it's probably a good thing to deprecate it because:
a) it's inferior to native traversals
b) cypher and gremlin does these things much better
2011/10/28 Peter Neubauer peter.neuba...@neotechnology.com
Hi all,
I think that the whole concept of
From the high church of REST, I have no objections.
Blessed be the Roy, for he hath delivered us from RPC. Or something.
Jim
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Also,
If we do that, I propose that we move the Cypher and Gremlin plugins into
server. WDYT?
On Oct 28, 2011 12:03 PM, Jim Webber j...@neotechnology.com wrote:
From the high church of REST, I have no objections.
Blessed be the Roy, for he hath delivered us from RPC. Or something.
Jim
If we do that, I propose that we move the Cypher and Gremlin plugins into
server. WDYT?
I'm ambivalent about that. What end-user benefits are there versus shipping
them as plugins?
Jim
___
Neo4j mailing list
User@lists.neo4j.org
Sent: Friday, October 28, 2011 7:16 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] REST traverse deprecation
Don't Bloat.
This also allows the plug-ins and language bindings to evolve at a difference
pace/cycle than the server. I'd say keep them separate.
-Original Message-
From: user
Thank you Max! The AREL for Cypher sounds very interesting!
Do you think the traversal rest api us doing its job for you given the power
of hhe häva version? I can even think if having a query method on the
embedded api so it fits...
On Oct 29, 2011 12:19 AM, maxdemarzi maxdema...@gmail.com
27 matches
Mail list logo
