Confirmed users
3,816
edits
Calendar:ITIP and iMIP Support: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Calendar iTIP and iMIP Design) |
No edit summary |
||
| Line 11: | Line 11: | ||
This phase realizes that the user has clicked on an email message with the text/calendar content type. It's goal is to present the message in some way so that the user realizes that this is no mere email message. Instead, it is presented as a simple HTML form. | This phase realizes that the user has clicked on an email message with the text/calendar content type. It's goal is to present the message in some way so that the user realizes that this is no mere email message. Instead, it is presented as a simple HTML form. | ||
[[Image: | [[Image:ITipDiag1_take2.png|Simplified diagram of current iTIP support]] | ||
=== Handling Phase === | === Handling Phase === | ||
| Line 36: | Line 36: | ||
A generalized sequence diagram for this model is as follows:<br> | A generalized sequence diagram for this model is as follows:<br> | ||
[[Image: | [[Image:IMipSecDiag.png|Simplified sequence diagram for iMIP Security Support]] | ||
Once the ltnMimeConverter is called, its job is to properly format the raw VCALENDAR data and present that data to the user, allowing the user to choose among appropriate actions in response to the method specified in the iTIP component. For example, the appropriate responses to a “REQUEST�? could be presented to the user as “Accept, Decline, Tentatively Accept, Reschedule�?. (See [[Calendar:iTIP_iMIP_Use_Cases]]). A different iTIP method will have a different set of appropriate actions, and should present a different set of options to the userthe appropriate actions will change. | Once the ltnMimeConverter is called, its job is to properly format the raw VCALENDAR data and present that data to the user, allowing the user to choose among appropriate actions in response to the method specified in the iTIP component. For example, the appropriate responses to a “REQUEST�? could be presented to the user as “Accept, Decline, Tentatively Accept, Reschedule�?. (See [[Calendar:iTIP_iMIP_Use_Cases]]). A different iTIP method will have a different set of appropriate actions, and should present a different set of options to the userthe appropriate actions will change. | ||
| Line 58: | Line 58: | ||
This interaction is sketched in the following sequence diagram.<br> | This interaction is sketched in the following sequence diagram.<br> | ||
[[Image: | [[Image:IMipPresDiag1.png|Simplified Diagram for iMIP Presentation Window]] | ||
=== New Handling Phase === | === New Handling Phase === | ||
| Line 83: | Line 83: | ||
The general sequence diagram of iTIP response handling would look like this:<br> | The general sequence diagram of iTIP response handling would look like this:<br> | ||
[[image: | [[image:ITipSeqProtocol.png|Simplified sequence diagram of iTIP handling]] | ||
==== VFREEBUSY and VJOURNAL Considerations ==== | ==== VFREEBUSY and VJOURNAL Considerations ==== | ||
| Line 92: | Line 92: | ||
=== Simplified User Interaction Overview === | === Simplified User Interaction Overview === | ||
In order to illustrate the entire sequence of events, here is a very simplified diagram, which attempts to show the user's interaction with these components.<br> | In order to illustrate the entire sequence of events, here is a very simplified diagram, which attempts to show the user's interaction with these components.<br> | ||
[[image: | [[image:ITipiMipoverview.png|Very simplified illustration of proposed iMIP and iTIP support with user interaction]] | ||
== Overview of Changes == | == Overview of Changes == | ||