1.1 --- a/docs/wiki/IncomingMessages Mon Oct 26 13:49:51 2015 +0100
1.2 +++ b/docs/wiki/IncomingMessages Mon Oct 26 14:05:25 2015 +0100
1.3 @@ -1,6 +1,9 @@
1.4 = Incoming Messages =
1.5
1.6 -When messages are received by the MTA for a recipient, imip-agent employs message rules in the MTA to provide handlers to inspect any calendar-related content and to update its records. Different handlers are provided to process incoming messages depending on the nature of the eventual recipient:
1.7 +When messages are received by the MTA for a recipient, imip-agent employs
1.8 +message rules in the MTA to provide handlers to inspect any calendar-related
1.9 +content and to update its records. Different handlers are provided to process
1.10 +incoming messages depending on the nature of the eventual recipient:
1.11
1.12 People:: Handled by the person handler
1.13 Resources:: Handled by the resource handler
1.14 @@ -12,62 +15,74 @@
1.15 For people, the operation of the person handler is as follows:
1.16
1.17 {{{#!table
1.18 -<rowspan="2"> '''Method''' ||
1.19 -<rowspan="2"> '''Effect on Objects''' ||
1.20 -<colspan="2"> '''Effect on Free/Busy''' ||
1.21 -<rowspan="2"> '''Effect on Request Queue'''
1.22 +<rowspan="2"> '''Method'''
1.23 +||<rowspan="2"> '''Effect on Objects'''
1.24 +||<colspan="2"> '''Effect on Free/Busy'''
1.25 +||<rowspan="2"> '''Effect on Request Queue'''
1.26 ==
1.27 ''for recipient's own record'' || ''for recipient's record of others''
1.28 ==
1.29 -`CANCEL` ||
1.30 -Set the state of the cancelled event, retaining it for future reference ||
1.31 -Remove record if the event is cancelled for the attendee (even if the event is not completely cancelled) ||
1.32 -<rowspan="3"> Update the recipient's free/busy record for the organiser ||
1.33 -Remove any queue entry
1.34 +`CANCEL`
1.35 +|| Set the state of the cancelled event, retaining it for future reference
1.36 +|| Remove record if the event is cancelled for the attendee (even if the event
1.37 +.. is not completely cancelled)
1.38 +||<rowspan="3"> Update the recipient's free/busy record for the organiser
1.39 +|| Remove any queue entry
1.40 ==
1.41 -`PUBLISH` ||
1.42 -<rowspan="2"> Add or update object, removing specific recurrences of recurring events ||
1.43 -<rowspan="3"> ||
1.44 -No modification to the queue
1.45 +`PUBLISH`
1.46 +||<rowspan="2"> Add or update object, removing specific recurrences of
1.47 + .. recurring events
1.48 +||<rowspan="3">
1.49 +|| No modification to the queue
1.50 ==
1.51 -`REQUEST` ||
1.52 -Add a queue entry for the event
1.53 +`REQUEST`
1.54 +|| Add a queue entry for the event
1.55 ==
1.56 -`REPLY` ||
1.57 -Merge attendee participation information ||
1.58 -Update the recipient's free/busy record for each of the attendees ||
1.59 -No modification to the queue
1.60 +`REPLY`
1.61 +|| Merge attendee participation information
1.62 +|| Update the recipient's free/busy record for each of the attendees
1.63 +|| No modification to the queue
1.64 }}}
1.65
1.66 -The effect of the person handler is to ensure that the user's record of the free/busy status for ''other participants'' reflects the consequences of those participants' stated attendance of events, and for the object records to reflect the most recent state of each event.
1.67 +The effect of the person handler is to ensure that the user's record of the
1.68 +free/busy status for ''other participants'' reflects the consequences of those
1.69 +participants' stated attendance of events, and for the object records to
1.70 +reflect the most recent state of each event.
1.71
1.72 -Note that the free/busy information for a recipient of an event is not generally changed when receiving a message. Such information is only definitively changed by recipients themselves when responding to incoming messages, and the [[../OutgoingMessages|outgoing messages]] processing is concerned with updating that information as such responses are sent.
1.73 +Note that the free/busy information for a recipient of an event is not
1.74 +generally changed when receiving a message. Such information is only
1.75 +definitively changed by recipients themselves when responding to incoming
1.76 +messages, and the [[../OutgoingMessages|outgoing messages]] processing is
1.77 +concerned with updating that information as such responses are sent.
1.78
1.79 For resources, the operation of the resource handler is as follows:
1.80
1.81 {{{#!table
1.82 -<rowspan="2"> '''Method''' ||
1.83 -<rowspan="2"> '''Effect on Objects''' ||
1.84 -<colspan="2"> '''Effect on Free/Busy''' ||
1.85 -<rowspan="2"> '''Effect on Request Queue'''
1.86 +<rowspan="2"> '''Method'''
1.87 +||<rowspan="2"> '''Effect on Objects'''
1.88 +||<colspan="2"> '''Effect on Free/Busy'''
1.89 +||<rowspan="2"> '''Effect on Request Queue'''
1.90 ==
1.91 ''for recipient's own record'' || ''for recipient's record of others''
1.92 ==
1.93 -`CANCEL` ||
1.94 -Set the state of the cancelled event, retaining it for future reference ||
1.95 -Remove record if the event is cancelled for the attendee (even if the event is not completely cancelled) ||
1.96 -<rowspan="4"> No records of other participants are employed by the resource handler ||
1.97 -<rowspan="4"> No queue is employed by the resource handler
1.98 +`CANCEL`
1.99 +|| Set the state of the cancelled event, retaining it for future reference
1.100 +|| Remove record if the event is cancelled for the attendee (even if the event
1.101 +.. is not completely cancelled)
1.102 +||<rowspan="4"> No records of other participants are employed by the resource
1.103 + .. handler
1.104 +||<rowspan="4"> No queue is employed by the resource handler
1.105 ==
1.106 -`PUBLISH` ||
1.107 -<colspan="2"> Ignored by the resource handler
1.108 +`PUBLISH`
1.109 +||<colspan="2"> Ignored by the resource handler
1.110 ==
1.111 -`REQUEST` ||
1.112 -Add or update object, removing specific recurrences of recurring events ||
1.113 -Attempt to schedule the event, creating or updating records for the recipient
1.114 +`REQUEST`
1.115 +|| Add or update object, removing specific recurrences of recurring events
1.116 +|| Attempt to schedule the event, creating or updating records for the
1.117 +.. recipient
1.118 ==
1.119 -`REPLY` ||
1.120 -<colspan="2"> Ignored by the resource handler
1.121 +`REPLY`
1.122 +||<colspan="2"> Ignored by the resource handler
1.123 }}}
1.124
1.125 == Other Object Types ==