- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 11 Jul 2005 19:58:35 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv26991
Modified Files:
ws-addr-core.xml
Log Message:
Added resolution to issue lc90 - clarified use of message id as uniqueness metric
Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.99
retrieving revision 1.100
diff -C2 -d -r1.99 -r1.100
*** ws-addr-core.xml 21 Jun 2005 17:46:03 -0000 1.99
--- ws-addr-core.xml 11 Jul 2005 19:58:33 -0000 1.100
***************
*** 400,404 ****
extension(s). When designing endpoint reference extensions designers should
consider whether they desire standard processing per this specification in cases
! where their extension is not recogonised or understood.</p>
</div2>
</div1>
--- 400,404 ----
extension(s). When designing endpoint reference extensions designers should
consider whether they desire standard processing per this specification in cases
! where their extension is not recognized or understood.</p>
</div2>
</div1>
***************
*** 806,810 ****
into the [address] or [reference parameters] properties.</p>
<p>Some processors may use message identifiers ([message id]) as part of a uniqueness
! metric in order to detect replays of messages. Care should be taken to ensure that
for purposes of replay detection, the message identifier is combined with other
data, such as a timestamp, so that a legitimate retransmission of the message is not
--- 806,810 ----
into the [address] or [reference parameters] properties.</p>
<p>Some processors may use message identifiers ([message id]) as part of a uniqueness
! metric in order to detect replays of messages. In this case, care should be taken to ensure that
for purposes of replay detection, the message identifier is combined with other
data, such as a timestamp, so that a legitimate retransmission of the message is not
Received on Monday, 11 July 2005 19:58:37 UTC