Well, the tradeoff here is that it breaks binary compatibility with the previous 4.1 beta releases.
I'm ok with removing it; we don't use it internally in the codebase anywhere anymore, and I think it's unlikely someone built a new storage backend that relied on it or tried to extend the cache module internals based on the beta release. I'd certainly like to avoid shipping new GA code where some of the new stuff is deprecated out of the starting gate. :) However, I'd like to hear Oleg's opinion on this -- he has pretty strong feelings about binary compatibility (certainly well-placed when talking about backwards compatibility for GA releases). Jon ________________________________________ From: sebb [[email protected]] Sent: Monday, January 10, 2011 7:51 PM To: HttpComponents Project Subject: .HttpCacheEntry.getVariantURIs() is deprecated - can we delete it? .HttpCacheEntry.getVariantURIs() is deprecated. Given that the class is @since 4.1, do we need to keep the method? If not, we should add Javadoc to say when it was deprecated and when will be removed --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
