|Re: [p2-dev] URLs, URIs, and IDs (oh my)|
RE: having one URI class used everywhere...I agree it would be attractive, but extension is difficult given URI class is final (to guarantee standards compliance among other reasons)...as in many cases means writing wrappers (anyway) to have new constructors, override other methods, etc.I'm not sure what extension is needed. can you elaborate or give an example?
ID: Extensible using OSGi/Equinox mechanisms...e.g. extension registry, adaptersI tihnk there are some extension registry things in the EMF URI world. Not sure what all they do. Perhaps Ed can elaborate.
URI: Impl has much functionality (already...yay), Standards compliant
API breakage aside, would it make sense to rephrase ECF API in terms of URIs?Cons:
ID: Another abstraction so has some impl cost
URI: Won't satisfy all use cases, so clients will still be creating/need to create own ID types (at least for some things like ECF connections)