Concurrent Long Spanning Edit Sessions using Change Lists with Explicit Assumptions

Abstract

An approach is provided that receives a change request from a requestor. The change request includes metadata regarding the change, one or more changes, and one or more change assumptions corresponding to at least one of the changes. The change request is stored in a data store of pending requests. One or more systems are identified that correspond to each of the change assumptions. The identified systems are automatically queried with queries that correspond to the change assumptions. Query responses in response to the querying are received from the identified systems. The validity of each of the change assumptions is determined based on the received query responses. If the change assumptions are valid, then the changes included in the change request are processed. On the other hand, if at least one of the change assumptions is invalid, then the change request is rejected.

1 . A computer-implemented method comprising:
 receiving a change request from a requestor, wherein the change request includes metadata regarding the change, one or more changes, and one or more change assumptions corresponding to at least one of the changes;   storing, in a nonvolatile storage medium, the request in a data store of pending requests;   identifying one or more systems that correspond to each of the change assumptions;   automatically querying one or more of the identified systems with one or more queries that correspond to the change assumptions;   receiving one or more query responses in response to the querying;   determining a validity, based on the received query responses, of each of the change assumptions;   processing the one or more changes included in the change request in response to determining that each of the change assumptions is valid; and   rejecting the change request in response to determining that at least one of the change assumptions is invalid.   
     
     
         2 . The method of  claim 1  wherein the change assumptions include one or more internal change assumptions and one or more external change assumptions, the method further comprising:
 determining the validity, based on the received query responses, of each checking an external validity of each of the external change assumptions, wherein each of the external change assumptions is checked against an external source, wherein the processing of the one or more changes is performed in response to determining that each of the internal change assumptions and each of the external change assumptions is valid. 
 
     
     
         3 . The method of  claim 2  further comprising:
 receiving, from one of the external sources, one or more assumption changes; and 
 modifying the one or more change assumptions based on the assumption changes received from the external source. 
 
     
     
         4 . The method of  claim 3  further comprising:
 prior to modifying the one or more change assumptions, verifying that the external source from which the assumption change was received is authorized to modify the change assumptions corresponding to the received assumption changes, wherein the modification of the change assumptions is performed in response to the external source being verified. 
 
     
     
         5 . The method of  claim 2  further comprising:
 re-determining the validity of each of the internal change assumptions after checking the external validity of each of the external change assumptions. 
 
     
     
         6 . The method of  claim 1  wherein the rejecting further comprises:
 preparing a message that includes one or more reasons corresponding to sending the prepared message to the requestor. 
 
     
     
         7 . The method of  claim 6  further comprising:
 incrementing a counter that tracks a number of times that the request has been rejected; 
 comparing the incremented counter with a predefined limit; 
 removing the request from the data store of pending requests in response to the comparison revealing that the request has been rejected the predefined limit of times; and 
 retaining the request in the data store of pending requests in response to the comparison revealing that the request has not been rejected the predefined limit of times, wherein the request is reprocessed after a predefined amount of time has passed.