1.1 --- a/docs/wiki/AgentPrograms Tue Nov 03 00:42:39 2015 +0100
1.2 +++ b/docs/wiki/AgentPrograms Tue Nov 03 18:09:26 2015 +0100
1.3 @@ -39,3 +39,25 @@
1.4 One exception is the `imip_person.py` program that needs to be told whether
1.5 it will deliver messages using [[../MailIntegration/LMTP|LMTP]] with the `-l`
1.6 option or using [[../MailIntegration/LocalSMTP|SMTP]] with the `-L` option.
1.7 +
1.8 +== Program Responsibilities ==
1.9 +
1.10 +The person agent programs or "handlers", `imip_person.py` and
1.11 +`imip_person_outgoing.py` are responsible for keeping the schedule of each
1.12 +participating calendar user up to date with the requests that are sent and
1.13 +received by that user. Their roles are limited to recording data along with
1.14 +a small amount of automation: they can be [[../Preferences|configured]] to
1.15 +reply to free/busy requests without requesting any intervention on the part
1.16 +of the user receiving such requests.
1.17 +
1.18 +Such handlers may be enhanced to perform more tasks autonomously, so that
1.19 +certain requests might be dealt with automatically, according to policies
1.20 +defined by each user. See the [[../UseCases|use-cases guide]] for some
1.21 +potentially-implementable ideas.
1.22 +
1.23 +Meanwhile, the resource handler, `imip_resource.py`, is responsible not only
1.24 +for maintaining a schedule for a resource, but it must also make scheduling
1.25 +decisions itself without human involvement. How it may behave is determined
1.26 +by a number of policies set in the [[../Preferences|preferences]] so that,
1.27 +for example, it may suggest alternative event periods when those requested
1.28 +in an invitation are unavailable.