The Neo4j REST Server - Part1: Get it going
blog.neo4j.org
The Neo4j REST Server - Part1: Get it going
1–8 of 8 posts
Re: The Neo4j REST Server - Part1: Get it going
#2So does that mean Neo4J can now be used in closed source projects?
Re: The Neo4j REST Server - Part1: Get it going
#3Awesome. I had to build this myself! Nice to see it as a feature now.
Re: The Neo4j REST Server - Part1: Get it going
#4A cool addition to a very useful project. That said, I prefer using JRuby and Neo4j in embedded mode: the Ruby bindings are very good.
Re: The Neo4j REST Server - Part1: Get it going
#5So does that mean Neo4J can now be used in closed source projects?
I don't think so. If the REST server is part of a larger system then I believe that the AGPL requires that the other networked software components need to be AGPLed.
They do have a commercial license (I think that they charge $1K for a 1-server perpetual commercial non-AGPL license).
Re: The Neo4j REST Server - Part1: Get it going
#6So does that mean Neo4J can now be used in closed source projects?
I don't think so. If the REST server is part of a larger system then I believe that the AGPL requires that the other networked software components need to be AGPLed. They do have a commercial license (I think that they charge $1K for a 1-server perpetual commercial non-AGPL license).
How about if the Neo4J REST component was (say) one of a few options (the others being something like FlockDB or a mysql implementation)... In effect you would need to bring your own Neo4J platform to use the larger sytem, and Neo4J would not be a core component of it.
Re: The Neo4j REST Server - Part1: Get it going
#7Earlier quoted context omitted.
I don't think so. If the REST server is part of a larger system then I believe that the AGPL requires that the other networked software components need to be AGPLed. They do have a commercial license (I think that they charge $1K for a 1-server perpetual commercial non-AGPL license).
How about if the Neo4J REST component was (say) one of a few options (the others being something like FlockDB or a mysql implementation)... In effect you would need to bring your own Neo4J platform to use the larger sytem, and Neo4J would not be a core component of it.
Good point, but I am not sure. The key thing is to respect the wishes of the authors of a package so I would just contact the Neo4j developers and ask them.
Re: The Neo4j REST Server - Part1: Get it going
#8Earlier quoted context omitted.
How about if the Neo4J REST component was (say) one of a few options (the others being something like FlockDB or a mysql implementation)... In effect you would need to bring your own Neo4J platform to use the larger sytem, and Neo4J would not be a core component of it.
Good point, but I am not sure. The key thing is to respect the wishes of the authors of a package so I would just contact the Neo4j developers and ask them.
I have posted on their mailing list.
However, I guess that if you dont distribute a copy of the Neo4J package with your code, they basically have no say?