Let's try this again. Using the +1 mechanism for a multipart email is tough so please include a comment on which part you are +1ing.
Also, I want to revise my suggestion to just call the directory 'geode-native' rather than 'geode-nativeclient'. Simply because I am lazy and don't want to type the extra 6 letters all the time. -Jake On Mon, Jan 16, 2017 at 8:26 AM Jacob Barrett <jbarr...@pivotal.io> wrote: > One of the first things necessary to get NC merged into the the develop > branch is understanding where it will go under the current geode project > structure. > > The quick and obvious solution is adding a 'geode-nativeclient` subproject > and relocating all the NC sources into that directory. > > Given that NC consists of two semi-distinct clients, C++ and .NET, it may > also make sense to organize more of a hierarchy. Consider: > geode-client/ > geode++ > geode.net > (or some other more creative names) > Keep in mind that today the .NET client is very tightly coupled with the > C++ client, so you can't build .NET without first building C++. > > My suggestion would be to do the quick and easy now and as we continue to > refine and refactor and hopefully write the .NET in pure CLI we make that > move them. Perhaps by that time there will be a pure Java client to include > in that structure. > > Thoughts? > > > -Jake > >
