-------- Original Message --------
Subject: RE: [ebxml-msg] Pull'ing a specific document
From: "Makesh Rao (marao)" <marao@cisco.com>
Date: Wed, March 31, 2010 1:18 pm
To: "David RR Webber (XML)" <david@drrw.info>
Cc: <ebxml-msg@lists.oasis-open.org>
Thanks David. I didn’t think of leveraging another service to make the Message available in messaging systems. I think it would be better to have just one request sent to the messaging system. More like what Pim suggested.
~Makesh
From: David RR Webber (XML) [mailto:david@drrw.info]
Sent: Tuesday, March 30, 2010 7:01 AM
To: Makesh Rao (marao)
Cc: ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Pull'ing a specific document
Actually I was suggesting two approaches. One is just the traditional backend application UserMessage - but the other is using a hybrid approach with a messaging queue and messaging service.
I've used this in production for a Grants.gov application built for NIH.
The actual messages packages are quite large - combination of XML and PDF attachments - so the original submission goes into the queue. The delivery system then allows external systems to query for messages waiting in the queue (actually this is a webservice via SOAP - but can easily be via ebMS too).
Having downloaded the current messages in the queue stack - then the external system issues requests to the messaging service - and it goes and gets those from the queue and delivers them.
-------- Original Message --------
Subject: RE: [ebxml-msg] Pull'ing a specific document
From: "Makesh Rao (marao)" <marao@cisco.com>
Date: Mon, March 29, 2010 9:12 pm
To: "David RR Webber (XML)" <david@drrw.info>
Cc: <ebxml-msg@lists.oasis-open.org>
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.