It specifically reminds me of tuple spaces. Regards, Michael On 8/29/06, Andy Little <andy@servocomm.freeserve.co.uk> wrote:
"Jeremy Pack" <Jeremy.Pack@sdl.usu.edu> wrote in message news:468EB9093DC44F4D9CBADE5C87BE5D1915FD8C@cobra.usurf.usu.edu...
The team_members are not dependent on the project_leader - they are depending on the information in the repository. The situation could be changed so that a certain team_member, or a higher level manager placed the information in the repository, and the team_member class would not need to be modified, as long as the meeting information structure was the same.
As I've designed it so far, the library has the following features:
-Data in the repository is indexed by strings
-Type-safe (type-safety across shared libraries may not work on all platforms, because of usage of RTTI. If I work to have this library reviewed for boost, this will need to be discussed)
-Thread-safety can be built into a variable in the repository (using boost.threads, variables can make automatic use of mutexes and such)
-Functions or functors can be used to verify that each data item in the repository stays in a consistent state (for instance, the repository can check that a number does not leave a certain range).
-A function or list of functions can be called when a value is updated - this can be used to implement the Observer pattern. Note that this could be used to provide for distributed repositories.
Isnt this quite close to the description of a database?
regards Any Little
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost