[
https://issues.apache.org/jira/browse/HTTPCLIENT-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920181#action_12920181
]
Oleg Kalnichevski commented on HTTPCLIENT-1005:
-----------------------------------------------
Jon
I am feeling really bad about having to lump all classes into one package.
What is your feeling about stability of the API at this point? How likely is it
that you may want to make sweeping changes to the classes and interfaces that
currently reside in o.a.h.client.cache? If you anticipate major changes , I'll
apply the patch and start working on the first BETA release. However, If you
feel that a few more months should be enough to finalize the API, we could
probably delay the BETA phase a little and do one more ALPHA meanwhile.
What do you think?
Oleg
> API surface of caching module can be reduced
> --------------------------------------------
>
> Key: HTTPCLIENT-1005
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1005
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: smaller-api.patch
>
>
> While the caching module can currently be considered functional and useful
> for folks as-is, there are several near-term enhancements planned that could
> change the exposed binary API of the caching module (although it is not yet
> clear whether they would or not). In an effort to allow the 4.1 GA release to
> go forward while hedging bets against future development, we should consider
> drastically reducing the exposed binary API of the caching module, and not
> exposing extension points until someone explicitly asks for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
