Hi,
The grammar for object type encoding in the 2.0 serialization spec
seems to be a bit loose compared to the 3.1.3 reference implementation:
O # object definition (#0)
t x00 x0b example.Car # type is example.Car
x92 # two fields
x05 color # color field name
x05 model # model field name
but when you serialize this using Hessian2Output in the 3.1.3 release,
the following sequence gets written out:
O, length(Type), number of fields, field name 1, field name 1
indicating that the production
t b16 b8 typestring
is actually
int typestring.
This does seem to be a more compact representation, but it differs
from the spec. Which one is right?
Thx,
Ben
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
