OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [ebxml-msg] Pull'ing a specific document

Hi David


So this will need to be a UserMessage rather than a Pull SignalMessage ? Backend implementation is something we have solution for, it was more on how to get the request for a particular package when Pulling data.





From: David RR Webber (XML) [mailto:david@drrw.info]
Sent: Monday, March 29, 2010 5:35 PM
To: Makesh Rao (marao)
Cc: ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Pull'ing a specific document




This sounds a bit like interfacing with an RSS server.  Otherwise this functionality is typically backend application enabled - from the payload - rather than the messaging system.


I know in RSS world people can pull delivery packages out of sequence - so priority items, or priority customers get handled first.  


I assume something similar to that is what they are looking - so it would require some customization involving a delivery queue - in combination with the messaging server - so that you instruct the queue to peel a package off and route it to the AS4 server for dispatch.  So the first thing you get is a notification of a package having been added to the queue - its size, priority and its queue id # - and then you issue a request message back to the server - and it releases it from the queue at that point for actual delivery.


Thanks, DW

-------- Original Message --------
Subject: [ebxml-msg] Pull'ing a specific document
From: "Makesh Rao (marao)" <marao@cisco.com>
Date: Mon, March 29, 2010 5:19 pm
To: <ebxml-msg@lists.oasis-open.org>



In initial conversations with partners/customers over AS4, I have repeatedly heard the request to be able to Pull a particular document. The unique identifier could be based on the UserMessage that has been exchanged earlier e.g. PO # if a PO Message has been sent earlier.


Is there provision in the current spec to be able to support that ? My  understanding is that it is a generic Pull where the next available document is sent in the response.


Any advice please ?




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]