rate
>>>>>>>>>> that use case instead?
>>>>>>>>>>
>>>>>>>>>> *Collecting our efforts in fewer buckets means that improvements
>>>> will
>>>>>>>>>> benefit everyone, not just the group
gt;>>>>>>>> /peter neubauer
>>>>>>>>>>
>>>>>>>>>> GTalk: neubauer.peter
>>>>>>>>>> Skype peter.neubauer
>>>>>>>>>> Phone +46 704 106975
&
t;>>> On Tue, Nov 1, 2011 at 9:19 AM, Andres Taylor
> > >>>>>>> wrote:
> > >>>>>>>> You, something like Neo4js <https://github.com/neo4j/neo4js>?
> > We've
> > >>>>> had
> > >>>>>>>>
artupbootcamp.org/ - Öresund - Innovation happens
>> HERE.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On Tue, Nov 1, 2011 at 9:19 AM, Andres Taylor
>> >>>>>>&g
, Nov 1, 2011 at 5:06 PM, Peter Neubauer <
> >>>>>>>> peter.neuba...@neotechnology.com> wrote:
> >>>>>>>>
> >>>>>>>>> Also,
> >>>>>>>>> there is another possibility: We are e
versal API into REST calls and then anyway executing script
>>>>>>>>> snippets, Why not exposing a JavaScript plugin along exactly the
>>> same
>>>>>>>>> lines as the Groovy plugin, and provide examples on how t
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:
> >
> > > * cus
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
gt; 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 plugin, and provide examples on how to use the
way?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> /peter neubauer
>>>>>>>>
>>>>>>>> GTalk: neubauer.peter
>>>>>>>> Skype peter.neubauer
gt;>>>> LinkedIn http://www.linkedin.com/in/neubauer
> >>>>>> Twitter http://twitter.com/peterneubauer
> >>>>>>
> >>>>>> http://www.neo4j.org - NOSQL for the Enterprise.
> >>>>>> http://startu
>>
>>>>>> On Tue, Nov 1, 2011 at 9:00 AM, Jacob Hansson
>>>>>> wrote:
>>>>>>> It would be interesting to rephrase the question like this:
>>>>>>>
>>>>>>> Are there any use cases that the REST traversal API covers, that we
>
> >> >
> >> >> > On Sun, Oct 30, 2011 at 2:45 PM, Peter Neubauer <
> >> >> > peter.neuba...@neotechnology.com> wrote:
> >> >> >
> >> >> >> Well,
> >> >> >> Andre
..@neotechnology.com> wrote:
>> >> >
>> >> >> 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 functio
; >> >> On Oct 29, 2011 6:47 PM, "maxdemarzi" wrote:
> >> >>
> >> >> > I think the traversal rest api is fine for my purposes, but if
> cypher
> >> is
> >> >> > where we wa
he 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 t
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
king of getting rid of the rest built in graph
>> algorithms
>> > or are those there to stay?
>> >
>> > --
>> > View this message in context:
>> >
>> http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-traverse-deprecation-tp
king of getting rid of the rest built in graph
> algorithms
> > or are those there to stay?
> >
> > --
> > View this message in context:
> >
> http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-travers
ithms
> or are those there to stay?
>
> --
> View this message in context:
> http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-traverse-deprecation-tp3460396p3464979.html
> Sent from the Neo4j Community Discussions mailing list archive at
> Nabble.com.
> _
graph algorithms
or are those there to stay?
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-traverse-deprecation-tp3460396p3464979.html
Sent from the Neo4j Community Discussions mailing list archive at Nabble.com
> right thing for Neo4j then do what you have to do.
>
> --
> View this message in context:
> http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-traverse-deprecation-tp3460396p3462201.html
> Sent from the Neo4j Community Discussions mailing list archive at
> Nab
-
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-traverse-deprecation-tp3460396p3462201.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
k Bullotta
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.
-
Webber
Sent: Friday, October 28, 2011 7:11 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] REST traverse deprecation
> 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
> 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
https://lists.neo4
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" 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
> __
>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
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
> Hi all,
> I think that the whole concept of
> http://docs.neo4j.org/chunked/snapshot/rest-api-traverse.html is
> brok
Hi all,
I think that the whole concept of
http://docs.neo4j.org/chunked/snapshot/rest-api-traverse.html is
broken, since it tries to emulate the embedded traversal logic in
REST, which is just broken.
With Cypher and Gremlin being MUCH better suited to do declarative and
scripted traversals, I thi
30 matches
Mail list logo
