> Good question. I'm not convinced I have a handle on what we expect in > our API. Are these JUST the for formal api's or does it also include > anything that's not implementation specific. If it's the former, than > they are not very usefull standalone since there are no entry points. . > .I was thinking that the api is the public interface which our typical > user will interact with. As such, I would think that we need to > eventually find a way to move our bootstrap listeners, filters, etc. . > to the api module.
I concur, I don't think its necessary to have a separate project to hold 10 classes most of which are interfaces that are already seperated by their namespaces alone (which is sufficient). If someone wants to implement outside of the core then they simply include the tiles-core and go from there. I'd like to see studies of people implementing a solution starting from an API outside of those submitted by Sun :-) Scot ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/
