OASIS ebXML Messaging Services TC

 View Only
Expand all | Collapse all

Groups - Transparent MEP routing proposal V0.1 (ebMS-transparent-Multihop-MEPs-Routng.doc) uploaded

  • 1.  Groups - Transparent MEP routing proposal V0.1 (ebMS-transparent-Multihop-MEPs-Routng.doc) uploaded

    Posted 03-25-2008 21:02
    A multi-hop proposal for MEPs. V0.1 focusing only on the Hub toplogy. No
    reliance on WS-Addressing for Hub-and-Spoke.
    
     -- Mr Jacques Durand
    
    The document named Transparent MEP routing proposal V0.1
    (ebMS-transparent-Multihop-MEPs-Routng.doc) has been submitted by Mr
    Jacques Durand to the OASIS ebXML Messaging Services TC document
    repository.
    
    Document Description:
    
    
    View Document Details:
    http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=27698
    
    Download Document:  
    http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/27698/ebMS-transparent-Multihop-MEPs-Routng.doc
    
    
    PLEASE NOTE:  If the above links do not work for you, your email application
    may be breaking the link into two pieces.  You may be able to copy and paste
    the entire link address into the address field of your web browser.
    
    -OASIS Open Administration
    


  • 2.  Re: [ebxml-msg] Groups - Transparent MEP routing proposal V0.1 (ebMS-transparent-Multihop-MEPs-Routng.doc) uploaded

    Posted 04-02-2008 20:18
    Jacques,
    
    in step 8 (section 2.1) you wirte that the hub uses the P-mode  
    associated with the message to determine whether the response should  
    be pushed to or is pulled by the endpoint. I assume this decision is  
    based on the PMode of the referred message and the values of the MEP  
    and MEPBinding properties of that P-mode?
    If so, doesn't this require, at least for the push request - pull  
    response case, specifying the MEP as Two-Way and the MEPBinding as  
    Push/Pull even for one-way MEPs?
    
    In section 2.2 you propose to use a new mpc for the responses and let  
    the endpoint pull them from that MPC. But how are you going to make  
    the distinction between two endpoints that both use the same service  
    at the other side of the hub, assuming this service will only use one  
    MPC ?
    This is not only an issue in this situation, but also more general.  
    When several MSH's use the same MPC, for example default, how can a  
    hub distinguish which message should be delivered on a pull signal  
    from one of the MSH's? As signal message don't carry enough  
    information on identifying the party the only way to do it is using  
    reftoMessageId. It would be a lot easier if signal messages also  
    contain a business header.
    
    Regards
    Sander
    
    
    
    On 25 mrt 2008, at 22:01, jdurand@us.fujitsu.com wrote:
    > A multi-hop proposal for MEPs. V0.1 focusing only on the Hub  
    > toplogy. No
    > reliance on WS-Addressing for Hub-and-Spoke.
    >
    > -- Mr Jacques Durand
    >
    > The document named Transparent MEP routing proposal V0.1
    > (ebMS-transparent-Multihop-MEPs-Routng.doc) has been submitted by Mr
    > Jacques Durand to the OASIS ebXML Messaging Services TC document
    > repository.
    >
    > Document Description:
    >
    >
    > View Document Details:
    > http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=27698
    >
    > Download Document:
    > http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/27698/ebMS-transparent-Multihop-MEPs-Routng.doc
    >
    >
    > PLEASE NOTE:  If the above links do not work for you, your email  
    > application
    > may be breaking the link into two pieces.  You may be able to copy  
    > and paste
    > the entire link address into the address field of your web browser.
    >
    > -OASIS Open Administration