Processing recurring events within personal information management clients

• US 8,271,577 B2
• Filed: 12/11/2011
• Issued: 09/18/2012
• Est. Priority Date: 12/29/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Barry, Nathan R.
• Primary Examiner(s): BLAIR, DOUGLAS B
• Application Number:
  US13/316,509
• Publication Number:
  US 20120084338A1
• Time in Patent Office: 282 Days
• Field of Search: 709/206, 709/246, 709/202, 709/205
• US Class Current: 709/202
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A computer-implemented method of processing recurring events within personal information management (PIM) clients can include executing a plug-in component within a PIM client. The method can include receiving, within the PIM client, an event update including a recurring event identifier that is natively understood by the PIM client and supplemental recurrence data not natively understood by the PIM client. The method further can include, responsive to the plug-in component detecting the supplemental recurrence data and a user input executing the event update, the plug-in component can locate a recurring event corresponding to the recurring event identifier. The method can include the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data, and storing the recurring event within the PIM client.

Claims

1. A computer-implemented method of processing recurring events within a personal information management (PIM) client, comprising:

executing a plug-in component within a PIM client;

receiving, within the PIM client, an event update comprising a first portion, natively understood by the PIM client, that specifies a recurring event identifier and a second portion including supplemental recurrence data not natively understood by the PIM client;

responsive to the plug-in component detecting the supplemental recurrence data and a user input executing the event update, the plug-in component locating a recurring event corresponding to the recurring event identifier;

the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data; and

storing the recurring event within the PIM client.

2. The computer-implemented method of claim 1, wherein

the PIM client stores a recurring event by representing each occurrence of the recurring event as an instance, wherein the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data further comprises iteratively updating selected instances for the recurring meeting according to the supplemental recurrence data within the event update.

3. The computer-implemented method of claim 1, wherein

the PIM client stores a recurring event as an occurrence of the event coupled with a repeat rule, wherein the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data further comprises creating a plurality of exceptions to the repeat rule according to the supplemental recurrence data within the event update.

4. The computer-implemented method of claim 1, further comprising

outputting an event update message comprising information indicating which occurrences of the recurring event are to be updated according to the supplemental recurrence data.

5. The computer-implemented method of claim 1, further comprising

outputting an update response message comprising information confirming which occurrences of the recurring event have been updated in the PIM client according to the supplemental recurrence data.

6. The computer-implemented method of claim 1, further comprising

the plug-in detecting an identifier within the event update indicating that supplemental recurrence data exists.

7. A computer-implemented method of creating recurring events within a personal information management (PIM) client, the method comprising:

executing a plug-in component within a PIM client;

receiving, within the PIM client, an event invitation comprising a first portion that is natively understood by the PIM client and a second portion comprising supplemental recurrence data not natively understood by the PIM client;

responsive to the plug-in component detecting the supplemental recurrence data and a user input accepting the event invitation, the plug-in component creating a recurring event according to the first portion and the second portion of the event update comprising the supplemental recurrence data; and

storing the recurring event within the PIM client.

8. The computer-implemented method of claim 7, wherein

the PIM client stores a recurring event by representing each occurrence of the recurring event as an instance, wherein the plug-in component creating a recurring event according, at least in part, to the first portion and the second portion of the event update comprising the supplemental recurrence data comprises iteratively adding a plurality of instances specifying the recurring event according to the supplemental recurrence data within the event invitation.

9. The computer-implemented method of claim 7, wherein

the PIM client stores a recurring event as an occurrence of the event coupled with a repeat rule, wherein the plug-in component creating a recurring event according, at least in part, to the first portion and the second portion of the event update comprising the supplemental recurrence data comprises creating a repeat rule specifying a plurality of occurrences for the recurring event according to the supplemental recurrence data within the event invitation.

10. The computer-implemented method of claim 7, further comprising

outputting an event invitation message comprising information indicating which occurrences of the recurring event are to be created according to the supplemental recurrence data.

11. The computer-implemented method of claim 7, further comprising

outputting an invitation response message comprising information confirming which occurrences of the recurring event have been created in the PIM client according to the supplemental recurrence data.

12. The computer-implemented method of claim 7, further comprising

the plug-in detecting an identifier within the event invitation indicating that supplemental recurrence data exists.

13. A computer program product comprising a computer usable storage device having stored therein computer usable program code for processing recurring events within a personal information management (PIM) client, the computer usable program code, which when executed by a computer hardware system, causes the computer hardware system to perform

executing a plug-in component within a PIM client;

receiving, within the PIM client, an event update comprising a first portion, natively understood by the PIM client, that specifies a recurring event identifier and a second portion including supplemental recurrence data not natively understood by the PIM client;

responsive to the plug-in component detecting the supplemental recurrence data and a user input executing the event update, the plug-in component locating a recurring event corresponding to the recurring event identifier;

the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data; and

storing the recurring event within the PIM client.

14. The computer program product of claim 13, wherein

the PIM client stores a recurring event by representing each occurrence of the recurring event as an instance, wherein the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data further comprises iteratively updating selected instances for the recurring meeting according to the supplemental recurrence data within the event update.

15. The computer program product of claim 13, wherein

the PIM client stores a recurring event as an occurrence of the event coupled with a repeat rule, wherein the plug-in component updating the recurring event according, at least in part, to the supplemental recurrence data further comprises creating a plurality of exceptions to the repeat rule according to the supplemental recurrence data within the event update.

16. The computer program product of claim 13, wherein the computer usable program code further causes the computer hardware system to perform

outputting an event update message comprising information indicating which occurrences of the recurring event are to be updated according to the supplemental recurrence data.

17. The computer program product of claim 13, wherein the computer usable program code further causes the computer hardware system to perform

outputting an update response message comprising information confirming which occurrences of the recurring event have been updated in the PIM client according to the supplemental recurrence data.

18. The computer program product of claim 13, further comprising

the plug-in detecting an identifier within the event update indicating that supplemental recurrence data exists.