SummaryThe system architecture of seeds of contempt is broken into two main components. The contempt component is the UI that manages workflow. The seed component controls resource and data management, and operates as a lightweight agent. In a typical use case, a user may use contempt to control a large number of seeds deployed over a multitude of networks and devices. ImplementationContempt Contempt is written using the Eclipse RCP framework, and presents visualizations using the prefuse toolkit. Eclipse RCP provides views and editors to a user. In contempt, views present the hierarchy of control presented by the seeds. Editors are used to display visual representations of resources managed by the seeds. This can be in the form of lists, or as prefuse visualizations. Seeds A seed provides two separate services. It provides an RMI service for control of the seed, and a derby database server for data management. RMI interfaces - SeedManager manages the loading and unloading of seeds
- BlueSeed manages a local network as if it was a resource
- RedSeed manages a remote network as if it was a resource
|
Sign in to add a comment
