Each programmer will have to develop his own internal mechanisms to manage the description, the interactivity and the behaviours of his multimedia documents. The lack of standard would forbid for instance to play in the same viewer several specific multimedia documents developped by different providers . However, for the transmission of such a MHEG object from a MHEG server to a MHEG client, the MHEG object has to be coded into the transmission language ASN.1. In the MHEG Client , the coded MHEG object has to be decoded. The MHEG Client has also to previously know how to manage the specific behaviour of the MHEG object since only the static description of the MHEG object is exchanged with ASN.1.
Internet provides the widespread environment for new multimedia applications.
However it needs to support data transmission with Quality Of Services . After many MHEG experiences, we decided to code our MHEG objects directlty in a Java representation. The main difference with other solutions using Java programming language in MHEG is to have a complete java implementation instead of using a classical ASN.1 intermediate format. As Java works on independent platform, a same Java coded representation of MHEG objects could be executed on different platforms without any recompilation. We use Java as an independent platform language to keep the ability to carry objects on heterogeneous platforms without the long coding and decoding ASN-1 phases.