Re: discussion priorities

[Henry Lowe <hlowe@omg.org>]

All,

I didn't see anything in the Messaging saying how routing is 
handled.  One of the things we've talked about since the 
beginning is multi-hop routing, e.g., customer at A orders 
widget W from vendor at V bu the message goes via a portal P
which means it travers two links (one of which might be HTTP
and the other MQSeries or CORBA).  

I included this in my comments, but didn't propvide text.  
You would probably use source routing for this sort of thing 
where the route(s) would be contained in the TPA.  But some 
how these have to get into the Header of the Message so A 
knows to send the message to P and P knows to send it on to V.
Also need to have a place in the headers to record it's 
actual wild and wooly route through the Internet for traceability.

Or is this all there and I just missed it?

Best regards,
Henry
---------------------------------------------
At 07:37 PM 08/21/2000 -0500, richard drummond wrote:
>I wish to vote on releasing the messaging spec to the wider ebXML audience
>this Thursday. given that we will incorporate "error handling" and the
>"party/address" codes in the spec during the comment period... does anyone
>think we can not pass the messaging spec this Thursday?
>
>best regards, Rik
>
>-----Original Message-----
>From: David Burdett [mailto:david.burdett@commerceone.com]
>Sent: Friday, August 18, 2000 7:17 PM
>To: ebXML Transport (E-mail)
>Subject: TRP Error Handling Spec Draft
>
>
>Folks
>
>I attach some light reading for the weekend. Alternatively called, the TRP
>Error Handling draft spec version 01 ;)
>
>David
> <<ebXML TRP Error Handling draft 01.doc>>  <<ebXML TRP Error Handling draft
>01.pdf>>
>
>Product Management, CommerceOne
>4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
>Tel: +1 (925) 520 4422 (also voicemail); Pager: +1 (888) 936 9599
>mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com
>
>