+1 for #2 We will need to be careful refactoring existing code if classes are sent over the wire.
-Dan On Mon, Oct 9, 2017 at 10:36 AM, Udo Kohlmeyer <u...@apache.org> wrote: > Hi there Geode devs, > > Whilst going through the code base I found that we have 2 differing > approaches of how we classify (or package structures) internal code. > > The first is /org.apache.geode.*INTERNAL*.module/ the other is > /org.apache.geode.module.*INTERNAL*/. > > Can anyone explain the difference to me and which one is the preferred > mechanism. I vote for approach 2, where the /*internal*/ package is defined > within the module/functional area. > > --Udo >