HuuHa!! Vaary Nice!
I'm definitely including those architectural options list documentation. I'm going to make sure I get the architectural use cases straight before I play with API's though. Incidentally, one thing that would be really helpful is if there were some intefaces that described how various architecural components of the ADS talk to each other. Just a brief summary of the key ones like, at start up this component does this using this API contract... Then during queries we use API to make calls on this component implementing this interface. That way it will be straightforward to create mockups of various ADS components and use them to test various API's for architectural consideration. This will be really good for 2.0 planning as well. I can do most of the work here, if someone wants to give me tips on where to look for stuff. --- Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Ole Ersoy a écrit : > > >Emmanuel: > > > >Each experimentation is warmly welcomed, if they > can > >bring some > >solution > >to a known problem ! > > > >Ole: > > > >Word - I'll consolidate these discussions into some > >type of design document, so that we have > standardized > >terminology / architecture use cases / and code > >examples to work from. > > > >I volunteered for the "How to help documentation, > >etc." JIRA entry anyways, so that will be a good > >start. > > > > Ole, > > there are tools that may worth a little > investigation : > http://jakarta.apache.org/jcs/index.html, an apache > cache manager > implementation > http://jakarta.apache.org/commons/transaction : A > transaction component > written by apache. > > I don't know how good they are, but at least JCS > seems to be around for > a while, and was written after JCache, the dormant > JSR-107 > > wdyt ? > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
