--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/91f5a3bc-a220-45ff-a466-57c198f43506%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
+1Makes sense that client libraries should be in a separate repo than the server:
- enables a separate release cadence
- allows for a different set of maintainers, even in the same org
- each client library will be written in a different language
Having said that, this means that we'll have to keep track of version compatibilities between client library versions + server versions. Hopefully, they will be mostly backwards-compatible until a major version change.
On Sat, Jul 28, 2018 at 11:06 AM, Jason Plurad <plu...@gmail.com> wrote:
Florian Hockmann is ready to contribute a .NET driver for JanusGraph. The pull request is currently found in the main janusgraph repo.
The driver extends the TinkerPop .NET driver with additional capability for JanusGraph types and predicates. In a previous dev list discussion thread, he and I discussed making a separate repository for this body of work. I propose the name janusgraph-dotnet for the repository.
Let's give it 72 hours for lazy consensus.
I'm +1 for this. Looking forward to getting better driver support as part of the broader project.
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/ec1b50bd-a22f-4f73-81c7-8fe7206dff87%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com.