Menu
▾
▴
Re: [ebxmlms-develop] Hermes 1.0: sync reply
|
From: Patrick Y. <kc...@ce...> - 2003-07-10 09:09:15
|
<!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 text="#000000" bgcolor="#ffffff">
Agreed to implement sync reply. It's a bit complicated. Let me try to
explain the difficulties here... (please bear with my poor English)..<br>
<br>
When Hermes is the sending out message, it normally will wait for the
HTTP response code. In case of the response message coming from the
same HTTP connection, Hermes can now handle it.<br>
<br>
When Hermes is receiving messages, by the current implementation, it
will close the HTTP connection after all data from the message has been
read. So, to implement sync reply, we should keep that connection in
memory without closing it. To be precise, there will be a mapping of
AppContext and HTTP connection kept in memory. Whenever the application
command to send out a message, that mapping is being looked up to see
any opened HTTP connection ready to use. If there is one, Hermes should
use that HTTP connection to send out the message. If not found, Hermes
should open a new connection.<br>
<br>
Here is the difficult part: when should we close that connection? Oh
yes, that should be controlled by a CPA parameter: syncReplyMode. The
possible values are mshSignalsOnly, signalsOnly, responseOnly,
signalsAndResponse, none. <br>
<br>
Easy for mshSignalsOnly. Since those ACKs are generated by Hermes,
after those ACKs has been sent, Hermes can then close the connection.<br>
<br>
For signalsOnly, responseOnly and signalsAndResponse, Hermes has no
idea about when to close the connection. The reason is Hermes does not
know the message being sent is actually a signal or a response.<br>
<br>
Our conclusion is, it is hard to manage the keep alive connection if
Hermes doesn't know about the business process.<br>
<br>
Any comments?<br>
<br>
Cheers, -Patrick<br>
<br>
<br>
<br>
Ronald van Kuijk wrote:<br>
<blockquote type="cite"
cite="mid...@po...">
<meta http-equiv="Content-Type" content="text/html; ">
<title>RE: [ebxmlms-develop] Hermes 1.0: sync reply</title>
<meta content="MSHTML 5.50.4916.2300" name="GENERATOR">
<div><span class="417445422-09072003"><font face="Arial"
color="#0000ff" size="2">Yes, but can the response come from an
application or only acks/errors . The last is currently the case or am
I wrong?</font></span></div>
<div> </div>
<div><span class="417445422-09072003"><font face="Arial"
color="#0000ff" size="2">Ronald</font></span></div>
<blockquote dir="ltr"
style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div class="OutlookMessageHeader" dir="ltr" align="left"><font
face="Tahoma" size="2">-----Oorspronkelijk bericht-----<br>
<b>Van:</b> Mayne, Peter [<a class="moz-txt-link-freetext" href="mailto:Pet...@ap...">mailto:Pet...@ap...</a>]<br>
<b>Verzonden:</b> donderdag 10 juli 2003 0:36<br>
<b>Aan:</b> '<a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a>'<br>
<b>Onderwerp:</b> RE: [ebxmlms-develop] Hermes 1.0: sync reply<br>
<br>
</font></div>
<p><font size="2">If I send a message over HTTP with SyncReply set,
Hermes will send a response back using the same HTTP connection. Is
this what you mean, or am I confused?</font></p>
<p><font size="2">PJDM</font> <br>
<font size="2">-- </font><br>
<font size="2">Peter Mayne</font> <br>
<font size="2">Technology Consultant</font> <br>
<font size="2">Spherion Technology Solutions</font> <br>
<font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font>
<br>
<font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p>
<p><font size="2">> -----Original Message-----</font> <br>
<font size="2">> From: Ronald van Kuijk [<a
href="mailto:rv...@ab...">mailto:rv...@ab...</a>] </font><br>
<font size="2">> Sent: Wednesday, 9 July 2003 7:14 PM</font> <br>
<font size="2">> To: '<a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a>'</font>
<br>
<font size="2">> Subject: RE: [ebxmlms-develop] Hermes 1.0: sync
reply</font> <br>
<font size="2">> </font><br>
<font size="2">> </font><br>
<font size="2">> I didn't really look into this, but afaik
SyncReply is not </font><br>
<font size="2">> implemented.</font> <br>
<font size="2">> To be able to use hermes in a web-service
(RPC?) like fashion, I think</font> <br>
<font size="2">> we should implement this (in a plugable way) as
wel.</font> <br>
<font size="2">> </font><br>
<font size="2">> Ronald</font> <br>
<font size="2">> </font><br>
<font size="2">> > -----Oorspronkelijk bericht-----</font> <br>
<font size="2">> > Van: Patrick Yee [<a
href="mailto:kc...@ce...">mailto:kc...@ce...</a>]</font>
<br>
<font size="2">> > Verzonden: dinsdag 8 juli 2003 10:32</font>
<br>
<font size="2">> > Aan: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font>
<br>
<font size="2">> > Onderwerp: [ebxmlms-develop] Hermes 1.0</font>
<br>
<font size="2">> > </font><br>
<font size="2">> > </font><br>
<font size="2">> > Dear all,</font> <br>
<font size="2">> > </font><br>
<font size="2">> > I drafted a document, which describe the
area we may need to </font><br>
<font size="2">> > re-engineer </font><br>
<font size="2">> > and the features we want to have in the
1.0 version. Please comment.</font> <br>
<font size="2">> > </font><br>
<font size="2">> > Regards, -Patrick</font> <br>
<font size="2">> > </font><br>
<font size="2">> </font></p>
<font color="blue" size="3">
<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>
</blockquote>
</body>
</html>
|
