Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Spaces/Naming"
(New page: {{CommentBox|This is a proposal for naming in spaces}} =Spaces URI= A Spaces URI consists of the following:<br/> <tt>:spaces:<i>provider scheme</i>:<i>location</i>:<i>space</i></tt> ==spa...) |
|||
| Line 17: | Line 17: | ||
Where <i>account</i> typically is a user specific part, and <i>address</i> is the address of a service provider. | Where <i>account</i> typically is a user specific part, and <i>address</i> is the address of a service provider. | ||
| + | =Hierarchical URI= | ||
| + | If a hierarchical URI is used from "provider scheme" forward, it is possible to reuse generic wizards for certain operations. | ||
| + | If a space provider needs to - an opaque URI can be used, but then wizards and API's are needed to be able to perform some | ||
| + | operations. | ||
=Examples= | =Examples= | ||
Revision as of 14:51, 14 January 2008
Spaces URI
A Spaces URI consists of the following:
:spaces:provider scheme:location:space
spaces
The spaces part is a keyword - it identifies the URI as specific to spaces.
provider scheme
A provider scheme is a scheme such as "local", "svn", "aol", "sourceforge". A plugin that provides a serviceProvider extension declares that it handles a particular provider scheme. At any given time there can only be one registered service provider extension for a provider scheme.
location
The format of the "location" part is determined by the service provider extension, and can can have any URI valid format. The only rule is that the very last part of the URI is reserved for the space name.
By convention, the location is on the format:
account@address
Where account typically is a user specific part, and address is the address of a service provider.
Hierarchical URI
If a hierarchical URI is used from "provider scheme" forward, it is possible to reuse generic wizards for certain operations. If a space provider needs to - an opaque URI can be used, but then wizards and API's are needed to be able to perform some operations.
Examples
spaces:svn:henrik.lindberg@spaces.cloudsmith.com:/demo
- spaces - keyword
- svn - use the space provider implementation for generic svn
- henrik.lindberg - the name of the user's account
- spaces.cloudsmith.com - location where the generic svn space is to be found
- /demo - the name of the space
spaces:local:demo
- spaces - keyword
- local - use the space provider implementation for local file system
- (empty) - the local scheme assumes "current user" and "localhost"
- demo - name of the space
etc.