Hi Alex, > Interesting... My main question is: what exactly is this package > offering to the end user in the current form? IMO it cannot be an > off-the-shelf product as there is no security. It is not a library > either, as extending it is not so easy. Basically, and without any > intention to harm any feelings, it looks like one of those dummy "web > UI interface to X". And I'd say it has much more potential than that!
All it offers at the moment is a way to connect Neo graphs to the big graph (aka WWW). That's all we had in mind for the first release. We had other features in mind for subsequent releases (which we'd cleverly codenamed crawl, walk, and run), but nobody's gotten round to them yet. TLS is always an option for security, but more fine-grained access would also be useful. That would be an interesting use-case for filters perhaps. > I think your initial assumption makes a lot of sense. But why would > one have to duplicate all the work when this could provide him not > only with a good example, but a common basis for a complete solution. Ah, that would be the "Neo server" aka "run" which hasn't yet been designed, let alone built. But you're right - at the moment the REST interface is basic. What form the full REST-ified server would take is still up for grabs. > I'm looking at it from the perspective of a DB vizualization tool: > what's in there offers you the default view. Next you could build your > own views, etc. You could even build your complete application using > it. RIght. That would be something like the traverser framework support I'd like to see go into the "walk" version of the interface. Or perhaps it's a JavaScript framework that goes into the "run" version of the server. I dunno - perhaps some kind of roadmap might be a good idea. > Does it make sense to you? Makes sense. Somebody (perhaps even me) just needs to find some time to do it. Jim _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
