imip-agent

Annotated docs/wiki/FreeBusyPublishing

1362:d96b4761e6f0
1014:fbe00dd6f971
2017-10-24 Paul Boddie file changeset files shortlog Remove superfluous result collection slicing and count method parameter.
paul@961 1 
= Free/Busy Publishing =
paul@961 2 
 
 paul@961      3 
Although iTIP [[http://tools.ietf.org/html/rfc5546#section-3.3|specifies]] the exchange
 
 paul@961      4 
of free/busy information through requests and replies, many mail-based calendar clients
 
 paul@961      5 
do not support these particular operations over e-mail when providing general
 
 paul@961      6 
[[http://tools.ietf.org/html/rfc6047|iMIP]] support. However, they may support the
 
 paul@961      7 
acquisition of free/busy information over HTTP.
 
 paul@961      8 
 
 paul@961      9 
The publishing of free/busy resources for users can be enabled by default in the
 
 paul@961     10 
[[../Configuration|configuration]] by changing the `PUBLISHING_DEFAULT` setting:
 
 paul@961     11 
 
 paul@961     12 
{{{
 
 paul@961     13 
PUBLISHING_DEFAULT = "publish"
 
 paul@961     14 
}}}
 
 paul@961     15 
 
 paul@961     16 
For this setting to have an effect, the `SHARING_DEFAULT` setting will need to be
 
 paul@961     17 
changed to enable free/busy sharing by default:
 
 paul@961     18 
 
 paul@961     19 
{{{
 
 paul@961     20 
SHARING_DEFAULT = "share"
 
 paul@961     21 
}}}
 
 paul@961     22 
 
 paul@961     23 
Users can enable sharing and publishing themselves by accessing their profile in the
 
 paul@961     24 
[[../CalendarManager|management interface]].
 
 paul@1014     25 
 
 paul@1014     26 
Depending on the [[../WebServerIntegration|Web server configuration]], resources are
 
 paul@1014     27 
made available at a location resembling the following:
 
 paul@1014     28 
 
 paul@1014     29 
{{{
 
 paul@1014     30 
https://webserver.example.com/freebusy/
 
 paul@1014     31 
}}}
 
 paul@1014     32 
 
 paul@1014     33 
Individual user data is published in locations like this:
 
 paul@1014     34 
 
 paul@1014     35 
{{{
 
 paul@1014     36 
https://webserver.example.com/freebusy/mailto%3Avincent.vole%40example.com/freebusy
 
 paul@1014     37 
}}}
 
 paul@1014     38 
 
 paul@1014     39 
Here, the `mailto:vincent.vole@example.com` identity has been URL-encoded. Web
 
 paul@1014     40 
browsers and mail programs may perform such encoding on a location given more
 
 paul@1014     41 
informally as follows:
 
 paul@1014     42 
 
 paul@1014     43 
{{{
 
 paul@1014     44 
https://webserver.example.com/freebusy/mailto:vincent.vole@example.com/freebusy
 
 paul@1014     45 
}}}
 
 paul@1014     46 
 
 paul@1014     47 
However, the properly-encoded version is regarded as the definitive version.