Re: [ebxmlms-develop] Sending/receiving acknowledgements

[Patrick Y. <kc...@ce...>]

MessageIn this case, maybe we can make it possible to pass in "null" as =
toMSHURL. -Patrick

  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Wednesday, April 30, 2003 6:53 AM
  Subject: RE: [ebxmlms-develop] Sending/receiving acknowledgements


  I don't have a problem with that at all. However, I should have the =
option of not providing a URL to the Request, because in many cases it =
is redundant and confusing.

  PJDM
  --
  Peter Mayne
  Technology Consultant
  Spherion Technology Solutions
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
  T: 61 2 62689727  F: 61 2 62689777=20
    -----Original Message-----
    From: Patrick Yee [mailto:kc...@ce...]=20
    Sent: Tuesday, 29 April 2003 7:50 PM
    To: ebx...@li...
    Subject: Re: [ebxmlms-develop] Sending/receiving acknowledgements


    If I use one Request object per recipient, and if I don't want the =
outgoing URL to be included in the messages (e.g. I want to use DUNS =
number as the To/From Party ID), it may be convenient to use the "last =
resort" URL. As such, I don't need to implement any ToURLResolver and =
rely only on the "last resort" one.

    Regards, -Patrick
The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any =
interference with,=20
use, disclosure or copying of this material is unauthorised and =
prohibited; and

(b) may contain personal information of the recipient and/or the sender =
as defined=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.