Given that the current source structure uses cpp and cli prefixes for the C++ and .NET clients, respectively, what about using cpp and cli for the directories, allowing any new .NET development to go into a separate directory (perhaps cs or csharp) without any additional moves?
Sarge > On 16 Jan, 2017, at 08:26, 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
