[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] The metadataRepositories extension point

I agree that URIs would be desirable over URLs.

One thing to point out though...there is no URI class in the CDC 1.0/Foundation 1.0 EE. That's the primary reason that the ECF filetransfer IFileIDFactory does not have a URI-based file id creation (it does have URL-based creation, of course), as we wanted this part of ECF 2.0.0 to support CDC 1.0/Foundation 1.0 EE.

But for future versions I'm generally happy to move to CDC 1.1/Foundation 1.1 as a minimum runtime for ECF filetransfer. And I can see that CDC 1.1/Foundation 1.1 is the minimum EE for other parts of p2 already.

Scott

Pascal Rapicault wrote:

It is exactly for the reason you have highlighted that we wanted to use URI instead of URLs and I want this to be fixed as we are starting shaping APIs



Inactive hide details for Thomas Hallgren ---06/13/2008 05:42:29 AM---On some places in the p2 API's there are comments regardiThomas Hallgren ---06/13/2008 05:42:29 AM---On some places in the p2 API's there are comments regarding perhaps using URI's instead of URL's. I



From: Thomas Hallgren <thomas@xxxxxxx>

To: 	
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Date: 	
06/13/2008 05:42 AM

Subject: 	
Re: [equinox-dev] The metadataRepositories extension point

------------------------------------------------------------------------



On some places in the p2 API's there are comments regarding perhaps
using URI's instead of URL's. I think that would be an excellent idea. A
URI is not tied to the existence of a particular scheme so for a
repository URI the scheme itself could be used to find the corresponding
repository factory. We use this approach successfully in the spaces
project where each space provider implements their own URI scheme.

At present, I need to use URL's that points to non-existent things so
that I eventually end up in my factory implementation where I can peruse
the URL for it to make sense. It works but it's not very clean (nor
efficient).

Regards,
Thomas Hallgren


Thomas Hallgren wrote: > I'm trying to understand how to use the > org.eclipse.equinox.p2.metadata.repository.metadataRepositories > extension point in order to register a factory for my new > IMetadataRepositoryFactory. From what I can see the current > implementation relies on a 'filter' called 'suffix' but I'm unable to > see the correlation between this filter and the URL that is used to > identify the repository. > > It would help me a great deal if someone could explain how I can make > sure that the MetadataRepositoryManager finds my new > IMetadataRepositoryFactory implementation. > > Thanks, > Thomas Hallgren > > > _______________________________________________ > equinox-dev mailing list > equinox-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


------------------------------------------------------------------------

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev