[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [provision] When must 'modify' return PSO-ID? (was"Re: [provision] bulkModify response.")
Ok, I want to flip-flop :-) Why worry about the sent value in this way - sounds computationally better to look for not null... So B for me too (now)! Darran Gary P Cole wrote: > Has anyone else given any thought to this question? Must a > modifyResponse contain PSO-ID *always* (or only when the PSO-ID has > been changed)? > Is it better to have a requestor: > A) compare returned PSO-ID against input PSO-ID? > B) check for non-null PSO-ID in modifyResponse? > > Darran supported A, but I think I might prefer B since: > - non-null seems a simpler check for the requestor. > - the provider knows whether it just changed the PSO-ID. > > gpc > Darran Rolls wrote: > >> Possibly clunky to make every response do it but I do like the >> simplicity aka must respond so always check it rather than some >> esoteric "sometimes". So I'm for MUST always return it in response... >> >> Darran >> >> Gary P Cole wrote: >> >>> We decided a week or so ago that a modify operation may change the >>> PSO-ID for a modified object. We decided that the modify operation >>> must therefore be able to return the PSO-ID for a modified object. >>> >>> 1) Must the modify operation *always* return the PSO-ID? Or must a >>> modify operation return the PSO-ID only if the modify operation >>> changes the PSO-ID? >>> >>> 2) I assume that bulkModify does NOT need to return any PSO-ID since >>> the requestor selects objects with a query (rather than with >>> identifiers). >>> >>> gpc >>> >>> >>> To unsubscribe from this mailing list (and be removed from the >>> roster of the OASIS TC), go to >>> http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php. >>> >>> >> >> To unsubscribe from this mailing list (and be removed from the roster >> of the OASIS TC), go to >> http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php. >> >> > > > > To unsubscribe from this mailing list (and be removed from the roster > of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]