dsml message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Proposed DSML 2 schema changes
- From: Jeff Parham <jeffparh@windows.microsoft.com>
- To: dsml@lists.oasis-open.org
- Date: Tue, 07 Aug 2001 17:00:46 -0700
Title: Message
The attached is a
strawman including the following proposed changes:
- Adds the model
attribute to the DSMLEnvelopeRequest element (see below).
- Fixes a typo
in the LDAPErrorCode enumeration.
- Adds controls
to the LDAPResult element. The LDAPResult element is used as the
response type for all operations other than searches and extended requests,
and per RFC 2251 all responses can contain controls.
- Incorporates the requestID proposed by John McGarvey
(IBM) and Christine Tomlinson (Sun). The only change from Christine's
representation is that the requestID
is an attribute rather than a child element. Incorporated John's suggestion that
the requestID can occur on envelopes as well as individual
requests/operations.
- Changes oc-class
from minOccurs=1 to minOccurs=0. This allows for DSML transformations of
LDAP search responses corresponding to search requests in
which typesOnly=true.
- Removes the dn
attribute from ExtendedResponse. (There is no such field in RFC 2251's
ExtendedResponse.)
The proposed
model attribute of the DSMLEnvelopeRequest has two possible values -- sync
and async. The sync value indicates that the responses corresponding
to all requests in the envelope must be bundled into a single
DSMLEnvelopeResponse -- i.e., the behavior described in the original MS
proposal. The async value indicates that the responses corresponding
to each request in the envelope may be sent asynchronously (using multiple
DSMLEnvelopeResponse elements if needed).
In addition I
propose that the specification document state the
following:
- A DSML
implementation MUST support model=sync or model=async.
- A DSML implementation MAY support both
model=sync and model=async.
- A DSML implementation MAY support mutliple operations per
DSMLEnvelopeRequest.
A DSML
implementation MAY support multiple responses per
DSMLEnvelopeResponse.
For example, this
would grant Microsoft the flexibility of not supporting the async model and
iPlanet the flexibility of not supporting batched
operations.
-J
dsmlv2_ms_20010807.xsd
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC