Re: [ebxmlms-develop] Non-delivery notification

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yes, I mean additional listeners to receive such information. Having
more listeners may make programming harder, but clearer.<br>
Regards, -Patrick<br>
<br>
<br>
Mayne, Peter wrote:<br>
<blockquote
 cite="mid...@s-..."
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <title>Message</title>
  <meta content="MSHTML 6.00.2800.1264" name="GENERATOR">
  <style></style>
  <div><font face="Arial" size="2"><span class="914102523-21032004">At
the moment, all communication with clients is done by sending an ebXML
message, whether it is a "real" message, or some kind of
notification/exception generated by the MSH itself. This has the
advantage of consistency, so that there only has to be one kind of
listener.</span></font></div>
  <div><font face="Arial" size="2"><span class="914102523-21032004"></span></font>&nbsp;</div>
  <div><font face="Arial" size="2"><span class="914102523-21032004">Or
did you mean something else by "channels"?</span></font></div>
  <div>&nbsp;</div>
  <div><span class="914102523-21032004"><font face="Arial" size="2">PJDM<br>
  </font></span><font size="2">--<br>
Peter Mayne<br>
Technology Consultant<br>
Spherion Technology Solutions<br>
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602<br>
T: 61 2 62689727&nbsp; F: 61 2 62689777</font> </div>
  <blockquote dir="ltr"
 style="border-left: 2px solid rgb(0, 0, 0); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
    <div class="OutlookMessageHeader" lang="en-us" dir="ltr"
 align="left"><font face="Tahoma" size="2">-----Original Message-----<br>
    <b>From:</b> Patrick Yee [<a class="moz-txt-link-freetext" href="mailto:kc...@ce...">mailto:kc...@ce...</a>] <br>
    <b>Sent:</b> Saturday, 20 March 2004 6:29 PM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a><br>
    <b>Subject:</b> Re: [ebxmlms-develop] Non-delivery notification<br>
    <br>
    </font></div>
    <div><font face="Arial" size="2">Agreed. This is a nice feature. I
have marked it down. To generalize the problem, do you think we need to
restructure the channels for the MSH server to report status to MSH
clients (e.g. failure notifications, sending success notifications,
error messages, etc.)? Any ideas?</font></div>
    <div>&nbsp;</div>
    <div><font face="Arial" size="2">Regards, -Patrick</font></div>
  </blockquote>
<!--[object_id=#ap.spherion.com#]-->
  <p align="left">&nbsp;</p>
  <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">The
information contained in this email and any attachments to it:</font></font></p>
  <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(a)
may be confidential and if you are not the intended recipient, any
interference with, <br>
use, disclosure or copying of this material is unauthorised and
prohibited; and</font></font></p>
  <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(b)
may contain personal information of the recipient and/or the sender as
defined <br>
under the Privacy Act 1988 (Cth). Consent is hereby given by the
recipient(s) to <br>
collect, hold and use such information and any personal information
contained in a <br>
response to this email, for any reasonable purpose in the ordinary
course of <br>
Spherion's <br>
business, including forwarding this email internally or disclosing it
to a third party. All <br>
personal information collected by Spherion will be handled in
accordance with <br>
Spherion's Privacy Policy. If you have received this email in error,
please notify the <br>
sender and delete it.</font></font></p>
  <p align="left"><font face="Tahoma" size="2"><font color="#0000ff">(c)
you agree not to employ or arrange employment for any candidate(s)
supplied in <br>
this email and any attachments without first entering into a
contractual agreement with <br>
Spherion. You further agree not to divulge any information contained in
this document <br>
to any person(s) or entities without the express permission of Spherion.<br>
  </font></font></p>
</blockquote>
<br>
</body>
</html>