| RE: [corona-dev] RepositoryDescriptor |
Currently the collaboration context container only knows about RepositoryDescriptor. This term is used as a general reference about anything. I like the idea of possibly renaming it to be more descriptive. The suggestion for "ContextProvider" has merit. Are there other items that the ContextContainer should contain? What about references to resources, or list of property values. I would like to make any changes to the ContextContainer in the next development cycle. ________________________________ From: corona-dev-bounces@xxxxxxxxxxx on behalf of Everitt, Glenn Sent: Mon 9/25/2006 4:18 PM To: Corona development Subject: [corona-dev] RepositoryDescriptor The name RepositoryDescriptor does not really describe the general way we are trying to allow information to be added to the ContextContainer. I was reading about the Eclipse Higgins project and they use the term Context Provider. It seems that ContextProvider makes more sense for something like a chat server or a web page then a RepositoryDescriptor to be put into a ContextContainer. I was wondering how annoyed everyone would be if we changed the RepositoryDescriptor to ContextProvider? It would mean regenerating the model and updating all the code that touched RepositoryDescriptor, but if we change it later the amount of work increases. Think about it before our meeting tomorrow. Glenn Everitt 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>>