Command propagation optimization

• US 9,979,682 B2
• Filed: 09/01/2015
• Issued: 05/22/2018
• Est. Priority Date: 09/01/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Singh, Jaskaran, Madejczyk, Szymon
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Maniwang, Joseph
• Application Number:
  US14/842,013
• Publication Number:
  US 20170063742A1
• Time in Patent Office: 994 Days
• Field of Search: 709206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]

Abstract

Providing series level updates for a series. A method includes identifying a master message. The master message is a series level message that includes a plurality of default properties for an ordered series. An ordered series of instance messages related to the series level message is identified. For each instance message in the ordered series of instance messages, one or more properties are identified that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message. A default property value from a corresponding property of the master message is propagated to each of the identified properties. The ordered series is propagated to one or more legacy clients that are unable to consume certain series level messages by propagating the ordered series of instance messages with the updated property values.

Claims

1. A system for providing series level updates for an ordered series of instance messages, the system comprising:

storage configured to store a master message, wherein the master message is a series level message that comprises a plurality of default properties for the ordered series of instance messages;

storage configured to store the ordered series of instance messages related to the series level message, wherein the ordered series of instance messages includes an instance message for each instance in the ordered series of instance messages;

one or more propagation entities configured to;

for each instance message in the ordered series of instance messages, identify one or more properties that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message; and

updating property values of the ordered series of instance messages by propagating a default property value from a corresponding property of the master message to each of the identified properties; and

wherein the system is configured to propagate the ordered series of instance messages to one or more legacy clients that are unable to consume a determined type of series level messages.

2. The system of claim 1, wherein the ordered series is a series of calendar items ordered temporally, and wherein the ordered series of instance messages are propagated to legacy clients that are unable to handle non-pattern recurrences of calendar items.

3. The system of claim 1, wherein the instance messages are email messages.

4. The system of claim 1, wherein the one or more propagation entities comprises an inline API of the system configured to allow a user to update series messages.

5. The system of claim 1, wherein the one or more propagation entities comprises a background agent configured to propagate default property value from a corresponding property of the master message to each of the identified properties.

6. The system of claim 1, wherein the one or more propagation entities comprises two different entities with one entity propagating default property values starting at a first ordered instance message in the ordered series of instance messages and proceeding towards a last ordered instance message in the ordered series of instance messages and the other entity starting at the last ordered instance message in the ordered series of instance messages and proceeding towards the first ordered instance message in the ordered series of instance messages.

7. The system of claim 6, wherein one of the two different entities is an inline API of a system configured to allow a user to update series messages and the other entity is a background agent.

8. The system of claim 1, wherein the instance messages are email messages conveying a calendaring message.

9. In a computing environment, a method of providing series level updates for an ordered series of instance messages to legacy clients that are unable to process a determined type of series level messages by propagating series level properties across the instance messages in the series of instance messages and providing the instance messages to the legacy clients, the method comprising:

identifying a master message, wherein the master message is a series level message that comprises a plurality of default properties for the ordered series of instance messages;

identifying the ordered series of instance messages related to the series level message, wherein the ordered series of instance messages includes an instance message for each instance in the ordered series of instance messages;

for each instance message in the ordered series of instance messages, identifying one or more properties that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message;

updating property values of the ordered series of instance messages by propagating a default property value from a corresponding property of the master message to each of the identified properties; and

propagating the ordered series of instance messages to one or more legacy clients that are unable to consume a first determined type of series level messages.

10. The method of claim 9, wherein the series is a series of calendar items ordered temporally, and wherein the ordered series of instance messages are propagated to legacy clients that are unable to handle non-pattern recurrences of calendar items.

11. The method of claim 9, wherein the instance messages are email messages.

12. The method of claim 9, wherein propagating the default property value is performed by using functionality of an inline API of a system configured to allow a user to update series messages.

13. The method of claim 9, wherein propagating the default property value is performed by using a background agent separate from a system configured to allow user updates to series messages.

14. The method of claim 9, wherein propagating the default property value is performed by using a two different entities with one entity propagating default property values starting at a first ordered instance message in the ordered series of instance messages and proceeding towards a last ordered instance message in the ordered series of instance messages and the other entity starting at the last ordered instance message in the ordered series of instance messages and proceeding towards the first ordered instance message in the ordered series of instance messages.

15. The method of claim 14, wherein one of the two different entities is an inline API of a system configured to allow a user to update series messages and the other entity is a background agent separate from a system configured to allow user updates to series messages.

16. The method of claim 9, wherein the instance messages are email messages conveying a calendaring message.

17. A system for providing series level updates for an ordered series of instance messages, the system comprising:

one or more hardware processors; and

one or more computer-readable hardware storage media, wherein the one or more computer-readable hardware storage media comprise computer-executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform the following;

identifying a master message, wherein the master message is a series level message that comprises a plurality of default properties for the ordered series of instance messages;

identifying the ordered series of instance messages related to the series level message, wherein the ordered series of instance messages includes an instance message for each instance in the ordered series of instance messages;

for each instance message in the ordered series of instance messages, identifying one or more properties that are not yet defined with default property values from the master message and that have not been defined as valid exceptions to the default properties from the master message;

updating property values of the ordered series of instance messages by propagating a default property value from a corresponding property of the master message to each of the identified properties; and

propagating the ordered series of instance messages to one or more legacy clients that are unable to consume a first determined type of series level messages.

18. The system of claim 17, wherein propagating the default property value is performed by using functionality of an inline API of a system configured to allow a user to update series messages.

19. The system of claim 17, wherein the system is configured such that propagating a default property value from a corresponding property of the master message to each of the identified properties is configured to be performed by using a background agent separate from a system configured to allow user updates to series messages.

20. The system of claim 17, wherein the system is configured such that propagating a default property value from a corresponding property of the master message to each of the identified properties is configured to be performed by using two different entities with one entity propagating default property values starting at a first ordered instance message in the ordered series of instance messages and proceeding towards a last ordered instance message in the ordered series of instance messages and the other entity starting at the last ordered instance message in the ordered series of instance messages and proceeding towards the first ordered instance message in the ordered series of instance messages.