| ODP: [corona-dev] Corona System Container |
Comments in blue. My concerns about this approach are: - system events will probably contain other set of messages than "normal" container; is there any common set of events between "normal" and system container? Is this really the case that we would need to distinguish system events from normal container events? If "system container" would be a context container containing set of repositories (pointing "sub-containers") then normal eventing seems sufficient. If you don't agree, maybe try to provide some example showing that we need something specific here. - the container will require a special handling - we shouldn't show it in PCX, user shouldn't open it, etc, it cannot be edited, etc. Special handling - that depends. Who could open and edit such system container? I would point on system administrators (is that true?). In such case we could have "system team" containing only user(s) with admin rights. System team members could open and edit such container. What do you think? Wouldn't it be easier to provide an other topic for system events? Marcin O'Flynn, Dennis napisał(a): > A need exists for components to communicate within the Corona > "system". This interaction will provide a "system" context enabling > collaboration about system actions and events. > > For example, when a new ContextContainer is created, the Corona server > needs to notify all Workbench clients of the availability of the new > container. > > The following is proposed: > > 1) The Corona server will create a special ContextContainer as the > default "system" container (SystemContainer) > > 2) All ContextContainers will be a repository definition within the > SystemContainer. > > 3) The SystemContainer will provide Corona administrative functions > via RepositryDescriptor for admin web service endpoints. > > 4) Any component interested in SystemContainer events will implement > container event handlers based upon Corona's container event model. > > The use of a SystemContainer will provide a consistent model for > Corona actions and events. Please give this idea some thought and post > feedback to this discussion thread. > > The contents of this e-mail are intended for the named addressee only. > It contains information that may be confidential. Unless you are the > named addressee or an authorized designee, you may not copy or use it, > or disclose it to anyone else. If you received it in error please > notify us immediately and then destroy it. > >------------------------------------------------------------------------ > >_______________________________________________ >corona-dev mailing list >corona-dev@xxxxxxxxxxx >https://dev.eclipse.org/mailman/listinfo/corona-dev > > The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. _______________________________________________ corona-dev mailing list corona-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/corona-dev The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
<<winmail.dat>>