DI Container and AOP Integration. The Core consists of a Component Container and AspectContainer. These are built in a fractal pattern in which all components of the system are composed. The core development future direction includes adaptation of external AOP systems such as AspectWerkz and supports the AOP alliance.
System Services - SwarmContainer, ApplicationContext, Base Level Services (Binding, Tcp) and Aspect (TcpClient, Multicast, Logging Management), Distributed ClassLoading, Class-relocation
Functionally Swarm-ONE is not yet complete. Further resolution is needed for:
JXTA provides a rich means of peer based networking. It supports the notion of super nodes which alleviate network floods. Further support is made for j2ME devices
Provide a means of operating as a client on device limited platforms
C# provisor for suitable serializer support
C++ provisor for suitable serializer support = may be represented as an network client
- Simple Chat - DumChat. (multiple container collusion)
- Simple WebApp - POJO version of PetShop (AOP, integration with servlets, persistence mechanisms)
- Mobile Agents - Distributed Agent farm that utilised agents to perform work. (code mobility)
- Distributed Build System - JUnit task that allows containers to execute tasks on remote containers and join responses. i.e. UnitTests on one box, then passing out multiple functional tests to all other developer machines (while idle) (adaptive execution, container collusion and cpu farming, coordination)
- Adaptive Work Scheduler - Given a set of work units, execute them by utilising available container(s) resources.(adaptation)
- Distributed OS - Swarm OS modelled on (U)nix to allow users to see other users, chat etc, and also fire of work units (bound to machines, unbound, parrallel) (distributed classloaders), support for Grid management. Commands might include, execute blah.class, kill, ctrlZ, jobs