search

calrissian / mango

Common utilities for rapid application development
Apache License 2.0
17 stars 7 forks source link

Mango URI's URI Resolver should be decoupled from the Stream transforms. #113

Closed cjnolet closed 8 years ago

eawagner commented 9 years ago

I tend to agree, that this should be done. Using the deprecation rules however between releases, this seems like a very annoying change to make. I would propose deprecating the whole package now without a replacement, with the goal of providing a well thought out design for this type of functionality to be added as a replacement.

cjnolet commented 9 years ago

Id personally like to get the new design in place and deprecate the old first. Gives an upgrade option. On Dec 25, 2014 2:42 PM, "eawagner" notifications@github.com wrote:

I tend to agree, that this should be done. Using the deprecation rules however between releases, this seems like a very annoying change to make. I would propose deprecating the whole package now without a replacement, with the goal of providing a well thought out design for this type of functionality to be added as a replacement.

— Reply to this email directly or view it on GitHub https://github.com/calrissian/mango/issues/113#issuecomment-68111412.

eawagner commented 9 years ago

The largest problem with this is that we either bastardize the current API to support deprecated and new design elements or create new classes/interfaces/package to house the new design. Maybe we come up with a new name instead of Resolver for its replacement, this would make a deprecation path easier.

Since the methods on the public interface for URIResolver are one of the main problems in question, simply changing this interface will force any implementations external to mango to change anyway and there isn't really a way to do that using a deprecation strategy to the current elements.