0002142: hessian draft comments

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002142

[Resin]

minor

always

11-05-07 09:05

11-05-07 15:59

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

Summary

0002142: hessian draft comments

Description

(rep by Charlie Groves)

I've been doing some work that involves parsing Hessian object
definitions, and have found a small difference between the example at
http://hessian.caucho.com/doc/hessian-serialization.html#anchor29 [^] and
the format used by Hessian2Output and Hessian2Input in
hessian-3.1.3.jar. The spec says an object definition starts with
'O' which is followed by a type definition starting with 't'.
However, both Hessian2Output and Hessian2Input move on to the two
bytes for String length following the 'O' and skip the 't'. I can
see the 't' isn't necessary as in the map and list case since the
type definition is mandatory for an object, but it'd be nice if the
spec were updated to reflect that. I'd actually prefer it if object
definitions were updated to be just an 'O' followed by a regular
Hessian string. That would shave off a byte in the most common case
where a type name is less than 32 characters and keep type
definitions confined to a single special case.

Additional Information

Attached Files

Relationships

Notes
(0002446) ferg 11-05-07 15:59	hessian/3943

Issue History
Date Modified	Username	Field	Change
11-05-07 09:05	ferg	New Issue
11-05-07 15:59	ferg	Note Added: 0002446
11-05-07 15:59	ferg	Assigned To	=> ferg
11-05-07 15:59	ferg	Status	new => closed
11-05-07 15:59	ferg	Resolution	open => fixed
11-05-07 15:59	ferg	Fixed in Version	=> 3.1.4

Mantis 1.0.0rc3[^]

28 total queries executed.
25 unique queries executed.