Hi,
I have the problem of receiving a message like this:-
----------------------------------
| ROSE OPERATION | ARGUMENT |
----------------------------------
The architecture I am looking to implement:-
1. Decode the header and identify the operation value
2. Use the operation value to decided which plug in to pass the raw
undecoded argument to.
3. Decode the argument in the plug in and act appropriately.
This seems to be a typical OSI style model - the first layer decoding the
outer part of the message; and then passing the inner message on to a
further layer.
However when I came to implement this - I find that I cannot find an
appropriate way to specify the argument part of the rose message - apart
from OCTET STRING. OCTET STRING seems to be frowned upon as an outmoded
way of specifying the hole in the packet.
The ROSE ASN.1 definitions seem to be geared towards defining the whole
packet at decode time - you cannot decode some of the packet without a
knowledge of the contents.
The design described above gives two stage decode - so that the orginal
layer that receives the message does not need to include the ASN.1 for the
argument. This means that I can then add future plug-in's without having
to change any code in original layer.
Does anyone have an answer to this ? (or should I use OCTET STRING *or*
change my architecture to decode the whole packet in one go ?)
Thanks
Bernard Kufluk, Websphere Voice Response for Aix, Hursley Park
[EMAIL PROTECTED] 01962 817643
