1.1 --- a/docs/wiki/Resources Fri May 13 15:41:38 2016 +0200
1.2 +++ b/docs/wiki/Resources Fri May 13 16:20:29 2016 +0200
1.3 @@ -70,6 +70,26 @@
1.4 periods of the resource's schedule. However, no attempt is made to reject the
1.5 booking of the resource according to the identity of the organiser.
1.6
1.7 +=== Concurrent Reservations ===
1.8 +
1.9 +The `schedule_in_freebusy` function causes a resource to attempt to schedule
1.10 +an event, and by default it rejects requests that involve periods for which
1.11 +the resource is otherwise committed. However, a resource can be allowed to
1.12 +attend (or commit to) multiple concurrent events.
1.13 +
1.14 +By indicating a value as an argument to the function, a kind of capacity or
1.15 +commitment level can be assigned to a resource. For example:
1.16 +
1.17 +{{{
1.18 +schedule_in_freebusy 5
1.19 +}}}
1.20 +
1.21 +This example indicates that a resource can support five different events
1.22 +occupying the same point in time. Applications of such concurrent reservations
1.23 +include things like rooms or resources that can be shared and which have a
1.24 +notion of a capacity that is not immediately exhausted as soon as one event
1.25 +seeks to reserve such a room or resource.
1.26 +
1.27 === Identity Controls ===
1.28
1.29 Although identity controls may be implemented in the e-mail system,