What is claimed is:
1. A coordinated push synchronization method, comprising the acts of:
detecting changes to a local application data store;
identifying a record affected by a detected change;
pushing the identified record;
ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated or deleted in a remote application data store through user-initiated synchronization; and
if not, updating the remote application data store with the pushed record.
2. The method of claim 1, wherein the act of ascertaining includes comparing a local change counter associated with pushed record with a remote change counter, where values for the local and remote change counters are equal the identified record, in its current form, has been replicated or deleted through user-initiated synchronization.
3. The method of claim 1, wherein the act of pushing the identified record comprises:
if the identified record has been detected as being new, pushing a replica of the identified record with instructions to save the replica in the remote application data store;
if the identified record has been detected as being modified, pushing a replica of the identified record with instructions to save the replica in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, pushing instructions to delete a prior version of the identified contained in the remote application data store.
4. The method of claim 1, further comprising, after updating the remote application data store, setting a coordination flag for the pushed record.
5. A coordinated user-initiated synchronization method, comprising the acts of:
detecting changes to a local application data store;
identifying a record affected by a detected change;
ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from a remote application data store through push synchronization; and
if not, synchronizing the remote application data store with the local application data store.
6. The method of claim 5, wherein the act of ascertaining includes examining a coordination flag associated with the identified record, a set coordination flag indicating that the identified record, in its current form, has been replicated in or deleted from the remote application data store through push synchronization and a reset coordination flag indicating that the identified record, in its current form, has not.
7. The method of claim 5, wherein the act of synchronizing comprises:
if the identified record has been detected as being new, replicating the identified record in the remote application data store;
if the identified record has been detected as being modified, replicating the identified record in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, deleting the version of the identified record from the remote application data store.
8. The method of claim 5, further comprising the act of altering a local change counter associated with a record affected by a detected change, and wherein the act of identifying comprises comparing a global change counter associated with the affected record with the local change counter associated with the affected record.
9. The method of claim 5, further comprising the acts of updating a value of a global change counter associated with the identified record to equal the value of a local change counter associated with the identified record, and resetting a coordination flag associated with the identified record.
10. A coordinated push and user-initiated synchronization method, comprising:
detecting changes to a local application data store;
identifying a record affected by a detected change;
if the identified record is pushed, ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from a remote application data store through user-initiated synchronization and, if not, updating the remote application data store with the pushed record; and
if a user initiates synchronization, ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from the remote application data store through push synchronization and, if not, synchronizing the remote application data store with the local application data store.
11. The method of claim 10, wherein the act of ascertaining whether the identified record has been replicated in or deleted from a remote application data store through user-initiated synchronization includes comparing a local change counter associated with the identified record with a remote change counter, the identified record, in its current form, has been replicated or deleted through user-initiated synchronization where values for the local and remote change counters are equal.
12. The method of claim 10, wherein the act of ascertaining whether the identified record has bee replicated in or deleted from the remote application data store through push synchronization includes examining a coordination flag associated with the identified record, a set coordination flag indicating that the identified record, in its current form, has been replicated in or deleted from the remote application data store through push synchronization and a reset coordination flag indicating that the identified record, in its current form, has not.
13. The method of claim 10, wherein the act of updating the remote application data store with the pushed record comprises:
if the pushed record has been detected as being new, replicating the pushed record in the remote application data store;
if the pushed record has been detected as being modified, replicating the pushed record in the remote application data store replacing a prior version of the pushed record contained in the remote application data store; and
if the pushed record has been detected as being deleted, deleting a prior version of the pushed record contained in the remote application data store.
14. The method of claim 10, wherein the act of synchronizing the remote application data store with the local application data store comprises:
if the identified record has been detected as being new, replicating the identified record in the remote application data store;
if the identified record has been detected as being modified, replicating the identified record in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, deleting the version of the identified record from the remote application data store.
15. The method of claim 10, further comprising, after updating the remote application data store with the pushed record, setting a coordination flag associated with the pushed record.
16. The method of claim 10, further comprising, after synchronizing the remote application data store with the local application data store is completed, updating a value of a global change counter associated with the identified record to equal the value of a local change counter associated with the identified record, and resetting a coordination flag associated with the identified record.
17. A coordinated push synchronization computer program product comprising a computer useable medium having computer readable instructions thereon for:
detecting changes to a local application data store;
identifying a record affected by a detected change;
pushing the identified record;
ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated or deleted in a remote application data store through user-initiated synchronization; and
if not, updating the remote application data store with the pushed record.
18. The product of claim 17, wherein the instructions for ascertaining include instructions for comparing a local change counter associated with the identified record with a remote change counter, where values for the local and remote change counters are equal the identified record, in its current form, has been replicated or deleted through user-initiated synchronization.
19. The product of claim 17, wherein the instructions for pushing the identified record comprise instructions for:
if the identified record has been detected as being new, pushing a replica of the identified record with instructions to save the replica in the remote application data store;
if the identified record has been detected as being modified, pushing a replica of the identified record with instructions to save the replica in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, pushing instructions to delete a prior version of the identified contained in the remote application data store.
20. The product of claim 17, further comprising instructions for, after updating the remote application data store with the pushed record, setting a coordination flag for the pushed record.
21. A coordinated user-initiated synchronization computer program product comprising a computer useable medium having computer readable instructions thereon for:
detecting changes to a local application data store;
identifying a record affected by a detected change;
ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from a remote application data store through push synchronization; and
if not, synchronizing the remote application data store with the local application data store.
22. The product of claim 21, wherein the instructions for ascertaining include instructions for examining a coordination flag associated with the identified record, a set coordination flag indicating that the identified record, in its current form, has been replicated in or deleted from the remote application data store through push synchronization and a reset coordination flag indicating that the identified record, in its current form, has not.
23. The product of claim 21, wherein the instructions for synchronizing comprise instructions for:
if the identified record has been detected as being new, replicating the identified record in the remote application data store;
if the identified record has been detected as being modified, replicating the identified record in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, deleting the version of the identified record from the remote application data store.
24. The product of claim 21, further comprising instructions for altering a local change counter associated with a record affected by a detected change, and wherein the instructions for identifying comprise instructions for comparing a global change counter associated with the affected record with the local change counter associated with the affected record.
25. The product of claim 21, further comprising instructions for updating a value of a global change counter associated with the identified record to equal the value of a local change counter associated with the identified record, and resetting a coordination flag associated with the identified record.
26. A coordinated push and user-initiated synchronization computer program product comprising a computer useable medium having computer readable instructions thereon for:
detecting changes to a local application data store;
identifying a record affected by a detected change;
if the identified record is pushed, ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from a remote application data store through user-initiated synchronization and, if not, updating the remote application data store with the pushed record; and
if a user initiates synchronization, ascertaining whether the identified record, in its current form as affected by the detected change, has been replicated in or deleted from the remote application data store through push synchronization and, if not, synchronizing the remote application data store with the local application data store.
27. The product of claim 26, wherein the instructions for ascertaining whether the identified record has been replicated in or deleted from a remote application data store through user-initiated synchronization include instructions for comparing a local change counter associated with the identified record with a remote change counter, the identified record, in its current form, has been replicated or deleted through user-initiated synchronization where values for the local and remote change counters are equal.
28. The product of claim 26, wherein the instructions for ascertaining whether the identified record has been replicated in or deleted from the remote application data store through push synchronization include instructions for examining a coordination flag associated with the identified record, a set coordination flag indicating that the identified record, in its current form, has been replicated in or deleted from the remote application data store through push synchronization, a reset coordination flag indicating that the identified record, in its current form, has not.
29. The product of claim 26, wherein the instructions for updating the remote application data store with the pushed record comprise instructions for:
if the pushed record has been detected as being new, replicating the pushed record in the remote application data store;
if the pushed record has been detected as being modified, replicating the pushed record in the remote application data store replacing a prior version of the record; and
if the pushed record has been detected as being deleted, deleting a prior version of the identified record contained in the remote application data store.
30. The product of claim 26, wherein the instructions for synchronizing the remote application data store with the local application data store comprise instructions for:
if the identified record has been detected as being new, replicating the identified record in the remote application data store;
if the identified record has been detected as being modified, replicating the identified record in the remote application data store replacing a prior version of the record; and
if the identified record has been detected as being deleted, deleting the version of the identified record from the remote application data store.
31. The product of claim 26, further comprising instructions for, after updating the remote application data store with the pushed record, setting a coordination flag associated with the identified record.
32. The product of claim 26, further comprising instructions for, after synchronizing the remote application data store with the local application data store have been executed, updating a value of a global change counter associated with the identified record to equal the value of a local change counter associated with the identified record, and resetting a coordination flag associated with the identified record.
33. A coordinated push synchronization system, comprising a push module and a reception module, the push operable to push a record and a local change counter associated with the record to the reception module, the reception module operable to compare the pushed local change counter with a remote change counter and to update a remote application data store with the pushed record based upon the comparison.
34. The system of claim 33, wherein the local and remote change counters each have a value and the reception module is operable to compare those values and update the remote application data store only if the values are not equal.
35. The system of claim 33, wherein the record is associated with a coordination flag, and wherein the push module is further operable to set the coordination flag upon updating the remote application data store with the pushed record.
36. A coordinated user-initiated synchronization system, comprising a synch module in communication with a synch engine, the synch module operable to detect the creation, modification, or deletion of or to a record and to modify a change counter according to the detection, the synch engine operable to examine the change counter and a coordination flag associated with the record and to issue instructions to replicate or delete the record on a remote system based upon the examination.
37. The system of claim 36, wherein the coordination flag has a status set or reset and wherein the synch engine is further operable to issue instructions to replicate or delete the record on the remote system only if the coordination flag is reset.
38. The system of claim 36, wherein the record is associated with a global change counter controlled by the synch engine and a local change counter controlled by the synch module, and wherein the synch engine is further operable to modify a value of the global change counter to equal a value for the local change counter upon issuing instructions to replicate of the record.
39. A coordinated push and user initiated synchronization system, comprising:
a push module and a reception module, the push module operable to detect the creation, modification, or deletion of a record, and to push the record and a local change counter associated with the record to the reception module, the reception module operable to compare the pushed local change counter with a remote change counter associated with the record and to update a remote application data store using the pushed record based upon the comparison;
a synch module operable to detect the creation, modification, or deletion of the record, to modify the local change counter based upon the detection and to reset the coordination flag; and
a synch engine in communication the local synch module, the synch engine operable to compare the local change counter with a global change counter associated with the record and to examine the coordination flag and to issue instructions to replicate or delete the record in the remote application data store based upon the comparison and examination.
40. The system of claim 39, wherein the local and remote change counters each have a value and the reception module is operable to compare those values and update the remote application data store only if the values are not equal.
41. The system of claim 36, wherein the coordination flag has a status set or reset, and the synch engine is further operable to issue instructions to replicate or delete the record in the remote application data store only if the coordination flag has a reset status.
42. The system of claim 39, wherein the push module is further operable to set the coordination flag upon updating the remote application data store with the pushed record.
43. The system of claim 36, wherein the synch engine is further operable to modify a value of the global change counter to equal a value for the local and remote change counters upon replication of the record on the remote system.
44. A coordinated push and user initiated synchronization system, comprising:
a means for detecting the creation, modification, or deletion of a record and pushing the record and a local change counter associated with the record;
a means for receiving the pushed record and local change counter, comparing the pushed local change counter with a remote change counter associated with the record, and updating a remote application data store using the pushed record based upon the comparison;
a means for detecting the creation, modification, or deletion of the record, modifying the local change counter, and resetting the coordination flag; and
a means for comparing the local change counter with a global change counter, examining the coordination flag, and issuing instructions to replicate or delete the record in the remote application data store based upon the comparison and examination.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method of inhibiting or reversing rejection or prolonging survival of an insulin-producing tissue graft by a human graft recipient, comprising the step of administering an effective amount of a CD40:CD154 binding interrupter to the human graft recipient, wherein the CD40:CD154 binding interruptor is an antibody or antibody derivative having the antigen-specific binding characteristics of the 5c8 antibody produced by ATCC Accession No. HB 10916.
2. (canceled)
3. (canceled)
4. A method of preserving function of grafted insulin-producing tissue or restoring function of impaired, grafted insulin-producing tissue in a human graft recipient, comprising the step of administering an effective amount of a CD40:CD154 binding interrupter to the human graft recipient wherein the CD40:CD154 binding interrupter is an antibody or antibody derivative having the antigen-specific binding characteristics of the 5c8 antibody produced by ATCC Accession No. HB 10916.
5. (canceled)
6. (canceled)
7. (canceled)
8. (canceled)
9. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is whole pancreatic tissue or isolated pancreatic islets.
10. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is a cell population comprising isolated adult islet B cells, isolated fetal islet d cells, cultured islet B cells, or immortalized islet B cells.
11. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is a cell population comprising host cells stably or inducibly expressing an insulin gene.
12. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is physically separated from tissues of the recipient by an immunoisolation device.
13. (canceled)
14. (canceled)
15. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is allogeneic to the graft recipient.
16. The method according to claim 1 or claim 4, wherein the insulin-producing tissue is xenogeneic to the graft recipient.
17. (canceled)
18. The method according to claim 1 or claim 4, wherein the human graft recipient is afflicted with an impairment of metabolic control of glucose metabolism.
19. The method according to claim 1 or claim 4, wherein the human graft recipient is afflicted with diabetes mellitus.
20. A method of restoring metabolic control of glucose metabolism in a human in need thereof, comprising the steps of:
a) implanting an effective amount of insulin-producing tissue in the human; and,
b) administering an effective amount of a CD40:CD154 binding interrupter to the human, wherein the CD40:CD154 binding interrupter is an antibody or antibody derivative having the antigen-specific binding characteristics of the 5c8 antibody produced by ATCC Accession No. HB 10916.
21. (canceled)
22. The method according to claim 20, wherein the antibody or antibody derivative is administered prior to tissue implantation.
23. The method according to claim 22, comprising the additional step of repeating administration of the antibody or antibody derivative at least twice within a two-week period following tissue implantation.
24. The method according to claim 23, comprising the further additional step of repeating administration of the antibody or antibody derivative at least one month after tissue implantation.
25. The method according to claim 24, comprising the still further additional step of repeating administration of the antibody or antibody derivative on a monthly basis, beginning at least two months after tissue implantation.
26.-39. (canceled)