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
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?
Let us assume the information in a Handle constitutes a GUID.
It constitutes both alpha-numeric characters (again, a Handle is just an
example to explain my point - could be any process in the life cycle of a
WSIA). The GUID will be higher case and could be lower case - a string in
either case should be uniquely same. For e.g.let assume you are passing a
parameter "WERTrrr429893484SFGSGGG....", which in a case-insensitive world the
parameter has the same value and meaning, and could be different in a
case-sensitive world (could even be construed as a totally different parameter
by the receving WS application).
There could be numerous other information that are being
passed through (at the operational level) - I am not concerned about what is
inside the XML/... messages (in the body). The information that is used for
processing at a header level in the context of WSIA.
From a WSIA point of view, could this be a requirement?
Srinivas Vadhri
-----Original Message-----
From: Rich
Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, April 30, 2002 10:49 AM
To:
wsia@lists.oasis-open.org
Subject: RE: [wsia] Marked
up requirements doc from F2F
Are you saying that the value of a Handle must be processed in
a case
insensitive manner? If so, why? Conceptually I
view a handle as an opaque
remote reference. If a
Consumer modifies it in any manner (such as changing
the case), I would view that as a security violation that should cause
the
Producer to refuse access to the referenced
item.
"Vadhri,
Srinivas"
<Srinivas.Vadhri@comme
To: Charles F
Wiecha/Cambridge/IBM@IBMUS,
rceone.com>
wsia@lists.oasis-open.org
cc:
04/30/2002 12:22
PM Subject:
RE: [wsia] Marked up requirements doc from
F2F
All,
I dont know if we had a requirement on case insensitiveness
(Upper and
Lower) of the web services applications? If
not, I think we should have one
under the General
Requirements. For e.g., if we are using the information
in
the Handle, the Consumer or Producer
application should process the
information in a case
in-sensitive manner.
Srinivas Vadhri
-----Original Message-----
From:
Charles F Wiecha [mailto:wiecha@us.ibm.com]
Sent: Monday, April 29, 2002 2:08 PM
To:
wsia@lists.oasis-open.org
Subject: [wsia] Marked up
requirements doc from F2F
Folks -- here's the marked up requirements document from the
face to face.
Sorry not to get this out sooner...let's
get the edits running on the email
list!
Charlie
(See attached file: WSIA reqs 2002-04-15.doc)
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the
subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC