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 "Corona Design Container Editing"
(→Context Container Editing) |
(→Context Container Editing) |
||
Line 1: | Line 1: | ||
==Context Container Editing== | ==Context Container Editing== | ||
− | The Context Container holds references to all the Repositories | + | The Context Container holds references to all the Repositories known by the container. The Context Container is shared with all of the users in a workgroup. |
+ | |||
+ | *All workgroup members in the Context Container Team Member repository have access to the Container definition. | ||
*The Context Container is stored on the Corona Server. | *The Context Container is stored on the Corona Server. |
Revision as of 10:52, 29 January 2007
Context Container Editing
The Context Container holds references to all the Repositories known by the container. The Context Container is shared with all of the users in a workgroup.
- All workgroup members in the Context Container Team Member repository have access to the Container definition.
- The Context Container is stored on the Corona Server.
- The Container Context should expose a web service interface so that it can be edited by authorized remote users in the workgroup.
- Authorized users in a workgroup should be allowed to add / remove repository defintions in the Context Container
- The Corona Container Editor should use the Web Service interface to modify the Container definition
- More than one user at a time should be able to edit the Context Container.
- The Context Container should send notifications that the Container has been changed so that Corona Client can update views using information from the Container
- Should we allow a Container to edited by a Corona Client when NOT connected to the Corona Server hosting the Context Container?
- If we do how should resolve potentially conflicting changes?