>> * require app devs to bundle their custom types in a dedicated jar also and >> to only reference them through interfaces, allow us to use the same approach >> as the one we're currently using > > I like one. It allows someone to leverage identity in there framework but > keeps it protected from leaking out to the user of the framework
I'm wondering how useful this is really going to be, are developers really going to want to write interfaces for all the types they use within express? Are they going to be able to hand over the lifecycle management (ie. not use DI etc). Those seem like pretty counter-intuitive restrictions to me that I personally wouldn't be happy about if they would be imposed on me. -- Geert Bevin Terracotta - http://www.terracotta.org _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
