Changes between Version 30 and Version 31 of SPIDocs
- Timestamp:
- Oct 13, 2014 10:41:59 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SPIDocs
v30 v31 70 70 The services in the SPI are: 71 71 ApiInfo:: 72 Version information and test interfaces. Client and server certificate distribution.72 Version information and client and server certificate distribution. 73 73 Admin:: 74 74 Low level testbed administration … … 190 190 Each user has a unique identifier, a textual ''userid''. Permissions, resources, objects, etcetera are all bound to that userid. A userid is a text string that uniquely identifies a user. A userid cannot contain the colon character (:) nor can it conflict with other userids or [wiki:SPIDocs#Projects projectids]. 191 191 192 A user creates a namespace for circles, experiments, and libraries. Instances of each of those abstractions are names as ''namespace'':''name''. A user with userid `u` can create experiments with names of the form `u:experiment`. This allows each user to manage their own names without introducing ambiguity when another user creates an experiment with the same name. Applications are welcome to hide the prefix on such names, except when needed to resolve an ambiguity. In such a case, t ehapplication may display only the parts of experiment names after the colon to user `u` unless that user also has access to another user's experiment with the same name after the colon. Such an application might display an experiment list to user `u` that looks like:192 A user creates a namespace for circles, experiments, and libraries. Instances of each of those abstractions are names as ''namespace'':''name''. A user with userid `u` can create experiments with names of the form `u:experiment`. This allows each user to manage their own names without introducing ambiguity when another user creates an experiment with the same name. Applications are welcome to hide the prefix on such names, except when needed to resolve an ambiguity. In such a case, the application may display only the parts of experiment names after the colon to user `u` unless that user also has access to another user's experiment with the same name after the colon. Such an application might display an experiment list to user `u` that looks like: 193 193 194 194 ||= Experiment Name =||