On Fri, Dec 2, 2011 at 3:55 PM, jadell <josh.ad...@gmail.com> wrote: > Quick question: > > Just saw this commit from Jake: > > http://github.com/neo4j/community/commit/f011c51fcbd5f12236fc633f57dcec9fb8cade83 > > Will the old Cypher plugin endpoint be going away, or will it remain for > back-compat? Which release will have the new endpoint? > > This will be helpful info for library authors. >
Damn Josh, you're quick :) We only talked briefly about how long we will be supporting the old plugin, but it will be *at least* through 1.6, and probably 1.7. The new endpoint will most likely be available as of the next milestone release. We've been told we're bad about making sure changelogs are properly updated, and we had a long talk about that today. We will be making sure that info on this, as well as deprecation plans for the old plugin, are properly included in the changelog for whatever release it becomes a part of. The new endpoint is in fact the same code as the plugin, so it should be reasonably easy to make the switch (should just be the URI change). The only caveat is that it does not currently support google table output like the plugin does. I haven't talked to Peter about if that should be included or not. /jake > Thanks, > > -- Josh > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Cypher-REST-endpoint-tp3554828p3554828.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 > -- Jacob Hansson Phone: +46 (0) 763503395 Twitter: @jakewins _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
