Hi Matthias, thanks for your reply.
> > "Envelopes may have headers that specify routing or other special > > processing information." [...] " The envelope syntax enables > > compression, encryption, signatures, and any routing or context headers > > to wrap a Hessian message." > > > > But unfortunately I did not find an example of a hessian message with an > > envelope and custom header information I could use for dynamic routing > > decisions. > I believe the quote refers to the very kind of transport protocol > envelopes/headers that you aim to avoid. Hmm, I hope you only believe that. ;-) Could you please elaborate why you believe this? Some examples for compression and encryption within the Hessian Envelope are given, so I hoped the same would apply to any routing or context headers. Maybe this is only part of the spec but not of the Java-API? I hope some hessian developer could shed some light on this. Is this the only mailing list regarding hessian (user/dev)? It seems to be quite silent. Regards, Eric _______________________________________________ hessian-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/hessian-interest
