Ole Ersoy a écrit :
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.
Well, err, hmmm, there is not so much such materials :(
What we have is here :
http://docs.safehaus.org/display/APACHEDS/Developer%27s+Guide
and you will have to dig...
Some partial infos :
http://docs.safehaus.org/display/APACHEDS/Interceptor+Mechanism
and here :
http://docs.safehaus.org/display/APACHEDS/ADS+2.0
http://docs.safehaus.org/display/APACHEDS/Partitions+implementation
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.
Alex ?
That way it will be straightforward to create mockups
of various ADS components and use them to test various
API's for architectural consideration.
Mockups are good to have ! I buy the idea :)
This will be really good for 2.0 planning as well.
Oooh yes !
I can do most of the work here, if someone wants to
give me tips on where to look for stuff.
Keep asking on the ML. We can feed you on the fly :)
Welcome on board, buddy :)
Emmanuel
