On 2 Dec 2007, at 21:38, Scott Ferguson wrote:
On Dec 2, 2007, at 1:01 PM, Ben Hood wrote:
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:
We did just change that.
When is this likely to be published? Is there going to be an
announcement?
The production should be
O, string (type), int (# of fields), field name 1, field name 2, ...
So the x0b is the string short code, not the byte value x0b (even
though they're the same code).
So a type with length 48 would use O S x00 x30 ...
OK, that's fine. By that token would the above example use
O x0b example.Car
or
O S x00 x0b example.Car
to use the compact string encoding?
-- Ben
-- Scott
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
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
