Folks I would like to start moving towards the freeze of 4.1 API. All new features added in trunk since 4.0 seem reasonably okay. The only thing that still blocks the 4.1-beta1 release is the the relatively untested API of the recently added caching module. I personally find it difficult to decide for myself whether the design is flexible enough unless there are other implementations (for instance, a file system or a ehache based) of the same API.
I see three different approaches we could pursue: (1) Take more time to stabilize HttpClientCache API at the price of delaying 4.1 GA. (2) Freeze the API of HttpClient and HttpMime and clearly state HttpClientCache is still experimental and its binary / API stability cannot be guaranteed, despite being a part of a GA release (3) Reduce the API to a bare minimum (make pretty much all but a few must-have classes package private, make protected methods of public classes private, etc) and gradually relax the restriction on class / method visibility as the module matures. What do you think? I am kind of leaning towards the last option. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
