Undelivered Mail Returned to Sender

This is the Postfix program at host caucho.com.

I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                        The Postfix program

<johnm-hessian@xxx.net> (expanded from <hessian-interest-mailout>): delivery
    temporarily suspended: Host or domain name not found. Name service error
    for name=non.net type=MX: Host not found, try again

attached mail follows:

Hello.

I have looked at new Hessian grammar at
http://wiki.caucho.com/Hessian_2.0_Grammar and have questions:

1. What does following notation mean?
int ::= [x80 - 0xcf]
Does it mean that these numbers represent themselves? If so what about
other numbers?

2. I do not understand what following double encodings represent
double ::= x06
       ::= x07
       ::= x08 b0
       ::= x09 b1 b0
       ::= x0b b3 b2 b1 b0
       ::= x0c b1 b0
       ::= x0e b3 b2 b1 b0
Double has to conform certain IEEE standard. So in these cases masks
for mantissa, exponent and sign should be specified. It does not seem
to be reasonable optimization since operations with such floating
numbers will be inefficient.

3. There is no protocol for querying protocol version from other
party. So implementations of Hessian protocol itself will be
incompatible. What for example implementation of version 1.0 would do
if it receives one of these new codes?

Scott Ferguson wrote:
> The next Resin snapshot will have a Hessian 2 implementation (probably
> Friday)
So I presume, Hessian 2.0 is not open for discussion anymore?

If it still possible to suggest something I would like to hear
opinions about encoding I described earlier:

>For "compressed" integer:
>'i' nnnddddd dddddddd .... (up to 9 elements)
>where 3 bits nnn represent number of bytes in the sequence - 1
>and remaining bits ddd... contain bits of required integer.
> For example:
> 0xfff => 'i' 00101111 11111111
> 0x3f3 => 'i' 00100011 11110011
> 0x3 => 'i' 00000011
> One reasonable variation here - instead of 3 use 4 bits for length
> representation thus covering even those cases that are beyond 'long'
> datatype.
It is possible to make similar shortened versions for length, long,
and ref.

It seems that Hessian 2.0 attempts to fill every gap in code space but
IMO this is not very wise as it lefts no space for manoeuvre in future.

--
Petr Gladkikh