[ Index ] [ Individual Project ] [ Placement Presentation ] [ Timetable ]

[ Index ] [ Research ] [ Schedule ]

A Distributed Java Version Control System

After reviewing Shakil Shaikh's project report it would only make sense to use his work as a base to my project and to extend it. He has provided the basis of a distributed java version control system, but still needs some work to make it a truly useful tool.

• Needs to be compatible with jar files, i.e. packages. This will provide additional information for versioning, maybe making the current method of storing versioning information redundant.
• Lack of security policy removes the useful of this tool in any real environment. Hopefully using JMX will provide some default level of security that can be fine tuned.
• Needs to test all the rules for binary compatibility.

The tool would have to be adapted into an mbean that would operate inside the JMX agent.

From my initial examination of the JMX spec (so far on the beans, not the agent or distributed serivces layer) it appears that rather than making each class an mbean, it would make more sense it create a wrapper mbean that handles the various jar files. The main reasoning for this is the conflicts between the design of a typical library class (minimal access) and the design of java beans (at least getter methods for each field).

Currently I've only considered reimplemented the tool using the JMX architecture. This by itself would not take a significant amount of time, and is unlikely to gain many marks so the next step (after finishing the JMX spec) will be to consider how I can make use of JMX to solve more of the problems in a distributed environment.