if someone
could let me know the best place to put them.
Would also be great if anyone else wants to join in and contribute to
improving the PHP REST client.
Thanks,
Todd Chaffee
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman
, before you can edit pages. You also have
to confirm your email address to get edit permission. /anders On
06/30/2011 11:03 AM, Todd Chaffee wrote:
I just wanted to remind folks that a PHP REST client based on Neo4j V1.3
has been available for some time at
http://github.com/tchaffee
That works for me. Thank you Peter.
- Todd
--
Message: 4
Date: Wed, 1 Jun 2011 13:48:52 +0200
From: Peter Neubauer peter.neuba...@neotechnology.com
Subject: Re: [Neo4j] Password sent in plain text via email?
To: Neo4j user discussions user@lists.neo4j.org
I was kind of shocked to see my password sent via email in plain text at the
bottom of the monthly mailing list notification from
mailman-ow...@lists.neo4j.org. Any way to suppress that part of the
message?
--
MIKAMAI | Making Media Social
http://mikamai.com
+447868260229
keep a generic API like we have now, but also allow index
implementations to expose extra API goodies in some reasonable way..
/jake
On Sun, May 1, 2011 at 4:12 PM, Todd Chaffee t...@mikamai.com wrote:
Hi Michael,
I actually appreciated the suggestion because it got me looking closer
This doesn't solve the lack of paging in the REST API, but it is a small
example of how I was able to limit the returned results for a large query.
Using the REST API query, looking for all nodes with the letter 'a'
somewhere in the name key, would look something like this:
curl -H
Just thought I'd weigh in on the paging of REST results. It's essential for
my app and is unfortunately forcing me to stick with mysql for part of the
app. I hope a couple of concrete examples will help.
1) Drop down AJAX type-ahead showing the first 4 results of searching for a
someone's name.
? Any suggestions on
improving the speed or am I stuck with mysql until paging is implemented in
the REST API?
Thanks,
Todd
On Tue, Apr 26, 2011 at 9:41 PM, Todd Chaffee t...@mikamai.com wrote:
Just thought I'd weigh in on the paging of REST results. It's essential
for my app
I am playing with release 1.3 (nice work!) and trying to get the PHP REST
implementation to work with the new named indexes. I noticed there is no
way to delete an index using the REST API?
From the java api I think this would be analogous to Index.delete()?
In the wild maybe it wouldn't be
Getting the same problem on Linux. Looks both like wrapper.jar and the
distribution specific wrapper jar file are missing from the download.
Unable to locate any of the following binaries:
/usr/local/src/neo4j-advanced-1.3/bin/wrapper.jar-linux-x86-32
Hi Peter,
I'll see if I can get me, Jake, and Olle all on board to finish the
refactoring and merge back with the original branch. Functionally the PHP
client works and is ready. We'd like to add unit tests and better organize
the code.
How about the REST api? Any word on whether the path
The long-term roadmap looks good. Don't have an opinion either way about
the format of the short-term road map or how much detail it should contain.
I somehow doubt anyone aside from the currently active developers will get
much out of the short-term details. Just my $0.02.
What are the next steps in moving towards getting the pathfinder GraphAlgo
REST APIs as part of the regular distribution?
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Hi David,
I've filed a bug report. I'm afraid I've gone about as far as I can in
understanding what the problem is and/or how to fix it without just guessing
that reducing the memory sizes could fix it, but don't know if that would
create side effects.
Thanks,
Todd
Hi Johan,
Output of java -version shows:
java version 1.6.0_18
OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1)
OpenJDK Client VM (build 16.0-b13, mixed mode, sharing)
Is that what you are looking for? I've also added this information to the
trac ticket.
Todd
Peter,
Thanks for taking a look at the code. I would love to see this moved to the
REST api, at least for the time being until a more robust approach can be
architected, for example one of the pluggable approaches you suggested.
If you can get the go-ahead from the rest of the team then it
Hi Mattias,
Could you supply some test case which can trigger it? That ShortestPath
algo
has been tested and even deployed in production environments with correct
behaviour.
Yes, I'll try to reproduce this with a small bit of java code. You could
also reproduce it immediately with any of
I've just checked-in a draft implementation of the REST API for
GraphAlgoFactory into the laboratory. It currently supports the following:
- algorithms shortestPath, allSimplePaths, and allPaths
- relationship expanders
- max depth (shortestPath seems to ignore this - there may be a bug
in
Hi Mattias,
Yes, I think that might be you I was referring to. I'll post any ideas or
questions I have to the mailing list as you suggested.
Todd
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Who should I contact to help add functionality to the neo4j REST
implementation?
I've been helping build a PHP client and the big missing piece now is the
neo4j algorithms which are not yet available in the REST implementation.
Thanks,
Todd
--
MIKAMAI | Making Media Social
http://mikamai.com
Peter,
That's a good approach. I've sent over the CLA.
My goal is simply to try to implement the org.neo4j.graphalgo
GraphAlgoFactory APIs in the REST interface.
*
*
My biggest concern is that it's been a while since I've done java
development. I could use some support from Mattias to discuss
21 matches
Mail list logo
