Menu
▾
▴
Re: [ebxmlms-develop] Should Hermes makes dispatching decision?
|
From: Patrick Y. <kc...@ce...> - 2003-06-23 10:14:35
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Most of the attributes are from CPA. But the current implementation is
a bit confusing.. I should admit. Some attributes are set at Request
object (session wide), some attributes are set at EbxmlMessage (i.e.
per message based). Luckily, there is no attribute being set at
property file (not configurable in run time).. ... <br>
<br>
We should make it consistent in 1.0.<br>
<br>
Regards, -Patrick<br>
<br>
<br>
Mayne, Peter wrote:<br>
<blockquote type="cite"
cite="mid...@s-...">
<meta http-equiv="Content-Type" content="text/html; ">
<title>Message</title>
<meta content="MSHTML 6.00.2800.1141" name="GENERATOR">
<div><span class="287353201-19062003"><font face="Arial" size="2">How
many of these are attributes of the CPA, and can therefore be
registered statically once, and how many are attributes of the
message, and therefore must be provided with a Request or message?</font></span></div>
<div><span class="287353201-19062003"></span> </div>
<div><span class="287353201-19062003"><font face="Arial" size="2">You've
said in another email that our concept is one Request per CPA. Isn't
the recipient URI a static attribute of the CPA? If that's the case,
then the Request doesn't need attributes such as the toMshUrl.</font></span></div>
<div> </div>
<div><span class="287353201-19062003"><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 F: 61 2 62689777</font> </div>
<blockquote
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> Wednesday, 18 June 2003 4:39 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] Should Hermes makes
dispatching decision?<br>
<br>
</font></div>
<blockquote
cite="mid...@s-..."
type="cite">
<div><span class="380443104-18062003"><font face="Arial" size="2">My
mistake, I didn't mean the question to refer to the application.
What I meant was that the specification says the MSH must respond
with an error if an unknown service/action is used, therefore the
MSH must know about the services and actions for a CPA. Are there
any other parameters that an MSH must know, so it can accept and
respond to messages correctly?</font></span></div>
</blockquote>
<br>
Off the top of my head, there are several: <br>
<br>
1. whether reliable messaging should be used or not, and the
corresponding parameters<br>
e.g. ackRequested = "always", "never", "perMessage"<br>
<br>
2. whether sync reply should be used for ACK, business message, or
both<br>
<br>
3. whether digital signature is requred<br>
<br>
There may be more, need to read spec for complete list.<br>
<br>
Regards, -Patrick<br>
<br>
------------------------------------------------------- This SF.Net
email is sponsored by: INetU Attention Web Developers &
Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers.
We Manage Them. You Get 10% Monthly Commission! INetU Dedicated
Managed Hosting <a class="moz-txt-link-freetext" href="http://www.inetu.net/partner/index.php">http://www.inetu.net/partner/index.php</a>
_______________________________________________ ebxmlms-develop mailing
list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></blockquote>
<font size="3" color="BLUE">
<pre>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,
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
under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to
collect, hold and use such information and any personal information contained in a
response to this email, for any reasonable purpose in the ordinary course of
Spherion's
business, including forwarding this email internally or disclosing it to a third party. All
personal information collected by Spherion will be handled in accordance with
Spherion's Privacy Policy. If you have received this email in error, please notify the
sender and delete it.
(c) you agree not to employ or arrange employment for any candidate(s) supplied in
this email and any attachments without first entering into a contractual agreement with
Spherion. You further agree not to divulge any information contained in this document
to any person(s) or entities without the express permission of Spherion.
</pre>
</font> </blockquote>
</body>
</html>
|
