MHonArc v2.5.2 -->

















wsia message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: RE: [wsia] Marked up requirements doc from F2F




From: Eilon Reshef <eilon.reshef@webcollage.com>
To: "'Vadhri, Srinivas'" <Srinivas.Vadhri@commerceone.com>,'Rich Thompson' <richt2@us.ibm.com>, wsia@lists.oasis-open.org
Date: Tue, 30 Apr 2002 16:14:58 -0400






Title: Message



I think we should at least consider putting a restriction on the 
character set (or, rather, byte range) used for the handle value, as this may 
simplify stuff on the Consumer's part, since if the Consumer is stateless 
it may decide to store the handle in a URL parameter or a form field, and if 
there's a limitation it might not need to encode the state. However, I would 
tend to agree with Rich that specifically regarding the handle, it should be 
treated as an opaque string, and thus even if it is case-insensitive (it might 
very well be so), the Consumer should not be allowed to make this assumption. Is 
there anywhere else where case-sensitivity is an issue?