On Mon, Mar 30, 2009 at 2:40 PM, Rickard Öberg <[email protected]> wrote: > Niclas Hedhman wrote: >> projects/qi4j/ >> api/ >> spi/ >> runtime/ >> bootstrap/ > > Do you see the tests as also being a part of this? Probably, right?
Yes. Forgot (who needs tests??). >>> * lib-cache: caching makes sense in two places I think: data and >>> computation. Data is already handled by the EntityStores, which leaves >>> computation, probably in services. Do we want a library for that, or >>> should >>> this be done by simply using a cache library in the implementation? >> >> Isn't the ESs delegating to this lib? > > No, this is not caching on that level. It has more to do with computation > caching, i.e. caching method results based on input parameters. > > We might want to do a specific EntityStore caching, for that purpose. Would > be very good to have. I need one right now for StreamFlow REST EntityStore, > on the client side. Ok, I have no opinion what to do... >>> * lib-uid: scrap, already exists as helper in SPI >> >> I disagree. I think in that case that the helpers in SPI should be tossed. > > So then basically all projects would have to have a dependency on this one? > Fine by me, just checking. Correct. One of the ideas with lib-uid is that there are alternate implementations, not only a 20+character long text, but IIRC there is a beginning of a sequence numbering one as well. > Alright, I'll do the suggested killings. Do you want to do the suggested > structure refactoring before 0.7? Yes, why not. That would force some more discipline into us. Such as responding to breakage in th Bamboo builds. We would also end up with separate versioning cycles, which IMHO is good. Cheers Niclas -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
