Re: Tempting..., very tempting...

On Tuesday, July 17, 2012 05:11:37 PM Jeroen van Meeuwen wrote:
> Hi there,
> 
> I'm almost finished implementing the delegation part of Resource Management,
> which is when "any car, not a specific car" is being made a reservation
> for.
> 
> The RFC 5546 iTip specification states, for the process of delegation, that:
> 
> - the delegator is to send back to the organizer a notification that the
> invitation is being delegated (done),
> 
> - the delegator is supposed to send an iTip to the delegatee (not
> implemented, this is a derivation from the spec already, but useless for
> our
> implementation),
> 
> - the delegatee then needs to send back his/her response (done).
> 

I forgot to mention, that the delegatee is also supposed to send its response 
back to the delegator, which is also not implemented (second slight derivation 
from spec... sigh).

A little background may be necessary - delegators' delegation and delegatees' 
acceptance is handled in one big swoop. Delegation only kicks in *after* we've 
verified that a slot is actually available for one or more of the individual 
non-unique resources in the collection. It seems (functionally) completely 
useless to therefor need to bounce back and forth a bunch of iTip messages - 
as they'll all end up in the same snippet of code that now handles it all.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08

_______________________________________________
Kolab-devel mailing list
[email protected]
https://www.intevation.de/mailman/listinfo/kolab-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEABECAAYFAlAFj40ACgkQKN6f2pNCvwjuwgCgqZvx4iavwwS3x66BlmHVqh4O
2uAAnA4jBPl/T/nRC3ZQXfz8pFFaD1kr
=861y
-----END PGP SIGNATURE-----