[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
________________________________
From: Marc Goodner [mailto:mgoodner@microsoft.com]=20
Sent: Thursday, Nov 03, 2005 9:38 AM
To: Patil, Sanjay; Yalcinalp, Umit; Christopher B Ferris;
ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] Proposal for i055
=09
=09
I agree the IT applies to the RMD as Umit proposed in i054. I do
not agree that the RMS needs to align any internal value it has in a way
that needs to be communicated back to the RMD. If the RMS has an
internal value it needs to align with the RMD IT value it should do so
internally to itself. The RMD knows what resources it has to properly
set the IT value. The RMS does not need to ask for a different IT value
from the RMD, it can either work within the bounds of the one the RMD
provides or not.
=20
There probably is text in the spec that needs to be clarified
that the IT is set at the RMD. I don't agree that the parameter itself
needs to be changed to support any alignment of values with the RMS.
=20
=20
=09
________________________________
From: Patil, Sanjay [mailto:sanjay.patil@sap.com]=20
Sent: Thursday, November 03, 2005 9:32 AM
To: Yalcinalp, Umit; Christopher B Ferris;
ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] Proposal for i055
=20
The value of IT at the RMD would specify how long the RMD should
wait for the next reliable message (argh!) to show up before giving up
on an open sequence. Where as I believe it is the RMS who is in a better
position to specify the time interval between the different messages it
intends to send out. So although the IT parameter would apply to the
RMD, it makes sense to allow the RMS to ask for a particular value for
IT (to be used by the RMD), IMHO.
=20
Thanks,=20
Sanjay
=20
=09
________________________________
From: Yalcinalp, Umit [mailto:umit.yalcinalp@sap.com]=20
Sent: Thursday, Nov 03, 2005 9:03 AM
To: Christopher B Ferris; ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] Proposal for i055
Chris,=20
=20
I think you missed the point and I possibly did not
clearify it.=20
=20
We are proposing to include IT for RMD for Policy
Attachment.=20
RMS may have its private IT, but what is specified and
applies to the endpoint applies to RMD.=20
=20
The interval definition we are proposing applies to RMD.
This information may be used in a private or optimized
way by RMS, which is a separate decision.=20
=20
Hopefully, this email makes it clearer.=20
=20
--umit
=20
=20
=09
________________________________
From: Christopher B Ferris
[mailto:chrisfer@us.ibm.com]=20
Sent: Thursday, Nov 03, 2005 8:54 AM
To: ws-rx@lists.oasis-open.org
Subject: Re: [ws-rx] Proposal for i055
=09
-1=20
=09
I don't see a need for the InactivityTimeout to
apply to the RMS. It is free to discard/terminate=20
a Sequence whenever it wants to do so. I am
preparing an alternate resolution to i055, but=20
we're still circling the wagons internally.=20
=09
Cheers,=20
=09
Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog:
http://webpages.charter.net/chrisfer/blog.html
phone: +1 508 377 9295=20
=09
"Yalcinalp, Umit" <umit.yalcinalp@sap.com> wrote
on 11/02/2005 04:48:57 PM:
=09
> Issue i055:=20
> This proposal is to resolve i055[1] based on
the clarification that=20
> we propose for resolution of Issue i054 [2].=20
> We observe that although the InactivityTimeout
should be specified=20
> by the RMD in the policy, it should be
possible for RMS to align its
> own inactivity timeout with respect to RMDs
specification of the timeout.=20
> In this regard, we propose to modify the
definition of=20
> InactivityTimeout which is currently a single
value. Instead, we=20
> propose that RMD should specify the
InactivityTimeout to be a range=20
> of values, with a lower and upper bound as
well as a default value.=20
> We think that this change will allow RMS to be
able to configure the
> IT to be able to send messages in an
appropriate interval to the=20
> RMD, still complying with the configuration of
the RMD. How this=20
> particular configuration may be addressed will
be the subject of a=20
> subsequent message as it is a separate issue
(i056 [3])=20
> We propose to add the following two attributes
to the definition of=20
> InactivityTimeout at Line 158 [4] and move the
specified value as=20
> the content value of the element as follows:=20
> Remove the lines 154-155 [4]=20
> {=20
>
/wsrmp:RMAssertion/wsrm:InactivityTimeout/@Milliseconds=20
> The inactivity timeout duration, specified in
milliseconds.=20
> }=20
> Replace the lines 151-153 with=20
> {/wsrmp:RMAssertion/wsrm:InactivityTimeout=20
> A parameter that specifies a period of
inactivity for a Sequence. If
> omitted, there is no=20
> implied value. The value of the element
indicates the default=20
> inactivity timeout duration in milliseconds.=20
> }=20
> Add the lines:=20
>
{/wsrmp:RMAssertion/wsrm:InactivityTimeout/@minValue=20
> A parameter that specifies a minimum value of
inactivity for a=20
> Sequence. If omitted, there is no=20
> implied value. This attribute is only present
when the @maxValue is present.=20
>
/wsrmp:RMAssertion/wsrm:InactivityTimeout/@maxValue=20
> A parameter that specifies a maximum value of
inactivity for a=20
> Sequence. If omitted, there is no=20
> implied value.=20
> }=20
> You probably noticed that we are also pointing
out a small=20
> problem/anomaly in the specification, where
the values are specified
> by attributes (i.e @Milliseconds attribute)
instead of element=20
> content. We propose that the definition of the
InactivityTimeout to=20
> be changed so that it should be using the
value of the element=20
> instead of the attribute. Further, minValue
and maxValue attributes=20
> are used to define a range.=20
> If the TC wishes to retain the usage of
attribute values instead of=20
> element content as proposed, it may be
retained along with minValue=20
> and maxValue proposal we are making. However,
we really want to know
> the rationale for which the values are
specified as attributes=20
> instead of elements contrary to the general
practice used today with XML.=20
>=20
> Thanks.=20
> --umit=20
> [1]
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i055
> [2]
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i054
> [3]
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i056
> [4]
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.
> php/14986/wsrmp-1.1-spec-wd-01.pdf=20
>=20
> ----------------------=20
> Dr. Umit Yalcinalp=20
> Standards Architect=20
> NetWeaver Industry Standards=20
> SAP Labs, LLC=20
> umit.yalcinalp@sap.com=20
> Tel: (650) 320-3095=20
------_=_NextPart_001_01C5E0A2.2A0A0270
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: sans-serif;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
TT {
FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>>> <FONT color=3D#000080>If the RMS has =
an internal=20
value it needs to align with the RMD IT value it should do so internally =
to=20
itself.</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><FONT =
color=3D#000080></FONT></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>That is a very provider centric model, which =
makes sense to=20
me in general (for example, we don't want to allow a consumer to =
arbitrarily=20
negotiate the provider WSDL at large!). But should we bar the consumer =
from=20
expressing its preferences in all =
circumstances? </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>From a techinal standpoint, I think of relialbe =
messaging=20
as more of a peer-to-peer model (as opposed to a strictly=20
almighty-provider-and-a-meeek-consumer model). We should consider =
allowing=20
exchange of policy preferences between the RMS and RMD, specifically =
when our=20
protocol has a well defined place (create sequence message exchange) for =
making=20
such bargains. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>What would be so wrong for an RMD =
implementation to employ=20
a standard default value for IT for all of its inbound sequences =
and still=20
allow the RMS to express a different value for the IT (to be applied at =
RMD)=20
based on the particular needs of the AS.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D542354117-03112005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sanjay<FONT =
size=3D2></DIV></FONT></FONT></SPAN><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Marc Goodner=20
[mailto:mgoodner@microsoft.com] <BR><B>Sent:</B> Thursday, Nov 03, =
2005 9:38=20
AM<BR><B>To:</B> Patil, Sanjay; Yalcinalp, Umit; Christopher B Ferris; =
ws-rx@lists.oasis-open.org<BR><B>Subject:</B> RE: [ws-rx] Proposal for =
i055<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I agree the =
IT=20
applies to the RMD as Umit proposed in i054. I do not agree that the =
RMS needs=20
to align any internal value it has in a way that needs to be =
communicated back=20
to the RMD. If the RMS has an internal value it needs to align with =
the RMD IT=20
value it should do so internally to itself. The RMD knows what =
resources it=20
has to properly set the IT value. The RMS does not need to ask for a =
different=20
IT value from the RMD, it can either work within the bounds of the one =
the RMD=20
provides or not.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">There =
probably is=20
text in the spec that needs to be clarified that the IT is set at the =
RMD. I=20
don’t agree that the parameter itself needs to be changed to =
support any=20
alignment of values with the RMS.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Patil,=20
Sanjay [mailto:sanjay.patil@sap.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, November 03, =
2005 9:32=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Yalcinalp, =
Umit;=20
Christopher B Ferris; ws-rx@lists.oasis-open.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ws-rx] Proposal =
for=20
i055</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The value =
of IT=20
at the RMD would specify how long the RMD should wait for the =
next=20
reliable message (argh!) to show up before giving up on an =
open sequence.=20
Where as I believe it is the RMS who is in a better position to =
specify the=20
time interval between the different messages it intends to send =
out. So=20
although the IT parameter would apply to the RMD, it makes sense to =
allow the=20
RMS to ask for a particular value for IT (to be used by the RMD), =
IMHO.</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Thanks,=20
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sanjay</SPAN></FONT><o:p></o:p></P>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
Yalcinalp, Umit [mailto:umit.yalcinalp@sap.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, Nov 03, 2005 =
9:03=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Christopher B=20
Ferris; ws-rx@lists.oasis-open.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ws-rx] Proposal =
for=20
i055</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Chris,=20
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think =
you missed=20
the point and I possibly did not clearify it. =
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">We are =
proposing to=20
include IT for RMD for Policy Attachment. =
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RMS may =
have its=20
private IT, but what is specified and applies to the endpoint =
applies to=20
RMD. </SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The =
interval=20
definition we are proposing applies to RMD. =
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">This =
information=20
may be used in a private or optimized way by RMS, which is a =
separate=20
decision. </SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hopefully, this=20
email makes it clearer. </SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">--umit</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
Christopher B Ferris [mailto:chrisfer@us.ibm.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, Nov 03, =
2005 8:54=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
ws-rx@lists.oasis-open.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ws-rx] =
Proposal for=20
i055</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt"><BR></SPAN></FONT><FONT =
face=3Dsans-serif=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
sans-serif">-1</SPAN></FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">I don't see a =
need for=20
the InactivityTimeout to apply to the RMS. It is free to=20
discard/terminate</SPAN></FONT> <BR><FONT face=3Dsans-serif =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">a Sequence =
whenever it=20
wants to do so. I am preparing an alternate resolution to i055, =
but=20
</SPAN></FONT><BR><FONT face=3Dsans-serif size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">we're still =
circling the=20
wagons internally.</SPAN></FONT> <BR><BR><FONT face=3Dsans-serif=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
sans-serif">Cheers,</SPAN></FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">Christopher=20
Ferris<BR>STSM, Emerging e-business Industry =
Architecture<BR>email:=20
chrisfer@us.ibm.com<BR>blog:=20
http://webpages.charter.net/chrisfer/blog.html<BR>phone: +1 508 =
377=20
9295</SPAN></FONT> <BR><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">"Yalcinalp, Umit" =
<umit.yalcinalp@sap.com>=20
wrote on 11/02/2005 04:48:57 PM:</SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><BR><TT><FONT=20
face=3D"Courier New">> Issue i055:=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> This proposal is to resolve i055[1] =
based on=20
the clarification that </SPAN></FONT></TT><FONT face=3D"Courier =
New"=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> we propose for resolution of Issue i054 =
[2].=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> We observe that although the=20
InactivityTimeout should be specified </SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> by the RMD in the policy, it should be =
possible=20
for RMS to align its</FONT></TT><BR><TT><FONT face=3D"Courier =
New">> own=20
inactivity timeout with respect to RMDs specification of the =
timeout.=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> In this regard, we propose to =
modify the=20
definition of </SPAN></FONT></TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> InactivityTimeout which is currently a =
single=20
value. Instead, we </FONT></TT><BR><TT><FONT face=3D"Courier =
New">>=20
propose that RMD should specify the InactivityTimeout to be a =
range=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> of values, =
with a lower=20
and upper bound as well as a default value. =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> We think that this change will allow RMS =
to be=20
able to configure the</FONT></TT><BR><TT><FONT face=3D"Courier =
New">> IT=20
to be able to send messages in an appropriate interval to the=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> RMD, still =
complying=20
with the configuration of the RMD. How this =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> particular configuration may be =
addressed will be=20
the subject of a </FONT></TT><BR><TT><FONT face=3D"Courier =
New">>=20
subsequent message as it is a separate issue (i056=20
[3])</FONT></TT></SPAN></FONT> <BR><TT><FONT face=3D"Courier New"=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> We propose to add =
the following=20
two attributes to the definition of </SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> InactivityTimeout at Line 158 [4] and =
move the=20
specified value as </FONT></TT><BR><TT><FONT face=3D"Courier =
New">> the=20
content value of the element as follows:</FONT></TT></SPAN></FONT> =
<BR><TT><FONT face=3D"Courier New" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt">>=20
Remove the lines 154-155 [4] </SPAN></FONT></TT><BR><TT><FONT=20
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> =
{=20
</SPAN></FONT></TT><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">>=20
/wsrmp:RMAssertion/wsrm:InactivityTimeout/@Milliseconds=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> The inactivity =
timeout=20
duration, specified in milliseconds. </FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> } =
</FONT></TT></SPAN></FONT><BR><TT><FONT=20
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> =
Replace the=20
lines 151-153 with </SPAN></FONT></TT><BR><TT><FONT =
face=3D"Courier New"=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt">>=20
{/wsrmp:RMAssertion/wsrm:InactivityTimeout =
</SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> A parameter that specifies a period of =
inactivity=20
for a Sequence. If</FONT></TT><BR><TT><FONT face=3D"Courier =
New">>=20
omitted, there is no </FONT></TT><BR><TT><FONT face=3D"Courier =
New">>=20
implied value. The value of the element indicates the default=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> inactivity =
timeout=20
duration in milliseconds. </FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> } =
</FONT></TT></SPAN></FONT><BR><TT><FONT=20
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> =
Add the=20
lines: </SPAN></FONT></TT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">>=20
{/wsrmp:RMAssertion/wsrm:InactivityTimeout/@minValue=20
</SPAN></FONT></TT><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> A parameter that specifies a minimum =
value of=20
inactivity for a </FONT></TT><BR><TT><FONT face=3D"Courier =
New">>=20
Sequence. If omitted, there is no </FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> implied value. This attribute is only =
present when=20
the @maxValue is present. </FONT></TT><BR><TT><FONT=20
face=3D"Courier New">>=20
/wsrmp:RMAssertion/wsrm:InactivityTimeout/@maxValue=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> A parameter =
that=20
specifies a maximum value of inactivity for a =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> Sequence. If omitted, there is no=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> implied value. =
</FONT></TT><BR><TT><FONT face=3D"Courier New">> }=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> You probably noticed that we are =
also=20
pointing out a small </SPAN></FONT></TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> problem/anomaly in the specification, =
where the=20
values are specified</FONT></TT><BR><TT><FONT face=3D"Courier =
New">> by=20
attributes (i.e @Milliseconds attribute) instead of element=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> content. We =
propose that=20
the definition of the InactivityTimeout to =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> be changed so that it should be using =
the value of=20
the element </FONT></TT><BR><TT><FONT face=3D"Courier New">> =
instead of=20
the attribute. Further, minValue and maxValue attributes=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> are used to =
define a=20
range. </FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier =
New"=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> If the TC wishes to =
retain the=20
usage of attribute values instead of </SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> element content as proposed, it may be =
retained=20
along with minValue </FONT></TT><BR><TT><FONT face=3D"Courier =
New">> and=20
maxValue proposal we are making. However, we really want to=20
know</FONT></TT><BR><TT><FONT face=3D"Courier New">> the =
rationale for=20
which the values are specified as attributes =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> instead of elements contrary to the =
general=20
practice used today with XML. =
</FONT></TT></SPAN></FONT><BR><TT><FONT=20
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> =
</SPAN></FONT></TT><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> Thanks. =
</FONT></TT></SPAN></FONT><BR><TT><FONT=20
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">> =
--umit=20
</SPAN></FONT></TT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> [1]=20
=
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i055 =
</SPAN></FONT></TT><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> [2]=20
=
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i054 =
</FONT></TT><BR><TT><FONT face=3D"Courier New">> [3]=20
=
http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i056 =
</FONT></TT><BR><TT><FONT face=3D"Courier New">> [4]=20
=
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.</FONT></TT><=
BR><TT><FONT=20
face=3D"Courier New">> php/14986/wsrmp-1.1-spec-wd-01.pdf=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> </SPAN></FONT></TT><FONT =
face=3D"Courier New"=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> ----------------------=20
</FONT></TT></SPAN></FONT><BR><TT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">> Dr. Umit Yalcinalp =
</SPAN></FONT></TT><FONT=20
face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR><TT><FONT=20
face=3D"Courier New">> Standards Architect =
</FONT></TT><BR><TT><FONT=20
face=3D"Courier New">> NetWeaver Industry Standards=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> SAP Labs, LLC=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> =
umit.yalcinalp@sap.com=20
</FONT></TT><BR><TT><FONT face=3D"Courier New">> Tel: (650) =
320-3095=20
=
</FONT></TT></SPAN></FONT><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></DIV>=
</BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C5E0A2.2A0A0270--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]