Is common-API for internal API's or external Api's? On Sep 25, 2007, at 8:01 AM, Alex Miller wrote:
> Seems like a good idea, but I would think common-api would be better. > > > ----- Original Message ----- > From: "Geert Bevin" <[EMAIL PROTECTED]> > To: [email protected] > Sent: Tuesday, September 25, 2007 9:46:52 AM (GMT-0600) America/ > Chicago > Subject: [tc-dev] TC system properties > > Hi, > > I was just reading through the source code and I noticed that the > system properties that are supported by Terracotta are really > scattered around the code base. Wouldn't it be good to create a > TerracottaProperties interface in the 'common' project that > consolidates all these property names as constants? Is 'common' the > correct project for this? Do all the other DSO projects depend on it? > > Thanks, > > Geert > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
