[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [provision] modify subscription request...
Jeff, I think this is just the price you pay without transactions. Probably the best that I can offer you is that the race condition that you mention could result in a Fault or exception. In my example interfaces I haven't listed faults but I can imagine a "conncurrentAccessFault" or something of that nature to signal this kind of condition. I'm not sure that directory servers can address this problem in any better way. With LDAP/DSML type systems you obviously have the ability to just specify the delete of a single attribute but you would still get a noSuchAttribute error under similar conditions. I have to agree that this is not an academic problem and I've seen some inventive ways of dealing with it. The most common in my experience is the use of timestamps to version the data but I don't think there's any perfect solution. Unless, that is, you have one? Gerry |---------+----------------------------> | | Jeff Bohren | | | <jbohren@opennetw| | | ork.com> | | | | | | 03/11/2003 06:39 | | | PM | | | | |---------+----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: provision@lists.oasis-open.org | | cc: | | Subject: [provision] modify subscription request... | | | >------------------------------------------------------------------------------------------------------------------------------| Gerry, Thee is something I have not been able to figure out in your proposal. For subscription targets that contain sequences of elements, how do you send a modify subscription request to remove one of the elements? You can't just resend the whole list because you may not have the current state of the subscription. Even if you queried for the current state of the subscription, another client could change it after you query for it, but before you send the update. To put this in perspective of the Tiny Telecom example, how would the RA web application remove a friends and familiy contact? BTW, this is not an academic question. In many systems that do RBAC, user role membership is often defined as a list roles on a user record (this is often the case for both LDAP and RDBMS based systems). One delegated administrator may grant (add) a role to a user while another revokes (removes) a different role from the same user. How would this type of provisioning operation be supported in you proposal? Jeff Bohren OpenNetwork Technologies ---------------------------------------------------------------- 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] | [List Home]