Hi Asankha,
Hi Eric
Sure, if you only want to route on the "To" address (Hessian
does not
seem to use any specific transport headers like SOAPAction etc),
What do you mean by the "To" address? Just the URL?
Yes, this means the scheme, hostname, port and path, from what I found
out looking briefly into Hessian, the Hessian payload is transported
over http (and https?).. but I did not come across any custom transport
(i.e. http) headers used by Hessian.. can you point me to any if they do
exist?
No, as far as I know the hessian protocol does not make assumptions
about the transport. We use the commons http client library as a
transport. So of course we could set HTTP headers. But I was thinking
about headers as part of the Hessian message.
The spec states the following:
"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."
Sure, but a sample message with the custom headers etc. that you have in
mind and the sample routing decision you want to make with the ESB would
be really useful at this point in time. I believe encryption,
compression and signatures etc. are all within the Hessian payload, and
thus hidden from the ESB use case scenarios you have in mind - am I
right?
Yes, encryption, compression and signatures are not what we have in
mind. We are thinking about the "any routing or context headers" part.
Unfortunately we have no sample message, as we currently use Hessian
without any header information we would need for CBR (so this is
something new), but I have seen some "writeHeader"-Methods in the API,
but had no time to investigate.
Of course this will be part of the Hessian message, but I don't know if
this will be easily accessible without haven to de-serialize the whole
message.
We only need to specify and access some custom header information and
use these as a
source for CBR and logging.
Are these http/s headers?
No I was not thinking about transport specific headers, but one could
also think about such a solution and its advantages and disadvantages.
I'm open for any discussion. My "feeling" tells me that such a low level
protocol wouldn't be the right place to put such information in. I don't
like the idea that any system in the middle might easily change or
remove such http header information. What do others think about this?
I'm going to contact the caucho guys and ask them about the usage of
their message envelope/header to store routing related information.
Regards,
Eric
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
