Versioning

Jtrix itself can be regarded as a central authority, with respect to the versions of the base layer. While there's no way around this, as one needs standards in order to communicate, this requirement confirms our philosophy that the Jtrix base API should be as small as possible, and openly available. Minimising the base API means that it will change less often. Each incompatible version of the base API effectively partitions our virtual platform and is to be avoided.

The component model provides a mechanism whereby components can be upgraded, and new or improved services supplied while maintaining backwards compatibility for older clients.