Done deal. Say
no more.
=========================================================
Darran Rolls
http://www.waveset.com
Waveset Technologies
Inc drolls@waveset.com
512) 657
8360
=========================================================
-----Original
Message-----
From: Jeff
Bohren [mailto:jbohren@opennetwork.com]
Sent: Friday, April 04,
2003 1:48
PM
To: Darran Rolls;
provision@lists.oasis-open.org
Subject: RE: [provision] Should
StatusRequest StatusReturns default be status
I think
there are good arguments for doing it either way. As I recall Doron felt
strongly that it should default to returning the results rather than just the
status. The way it is now is how the motion was worded when we added
this.
Jeff
Bohren
Product
Architect
OpenNetwork
Technologies, Inc
-----Original
Message-----
From: Darran
Rolls [mailto:Darran.Rolls@waveset.com]
Sent: Friday, April 04,
2003 2:45
PM
To:
provision@lists.oasis-open.org
Subject: [provision] Should StatusRequest
StatusReturns default be status
In the latest draft schema we have
added the StatusReturns attribute to StatusRequets with possible values of
status & results. This attribute is optional with a default
value of Results. This implies that unless the client states otherwise
they will always get the current results set on s statusrequest. Should
this be the other way around?
Thanks
=========================================================
Darran
Rolls
http://www.waveset.com
Waveset Technologies
Inc drolls@waveset.com
512) 657
8360
=========================================================