On Mon, 2008-10-20 at 18:22 +0200, Julien Kerihuel wrote:
> I've pushed in r820 some code which provides access to users FreeBusy
> data and let you retrieve and dump it. A preliminary implementation has
> been added to openchangeclient:

I've introduced a new convenient function named IsFreeBusyConflict in
r823. This function checks if a date pointed by a FILETIME * conflicts
with published FreeBusy Busy/Out Of Office data.

I've added this behavior to openchangeclient --sendappointment so it now
- by default - stops creating the event if either the start of end date
conflicts. In the meantime this behavior can be overridden using the
--force option.

If you feel like this is more a limitation than an enhancement, please
post a comment on the list. Furthermore the code being yet preliminary,
I'm looking for beta testers who could point out some bugs and give
feedback.

For example:
==============
[EMAIL PROTECTED] trunk]$ ./bin/openchangeclient --freebusy=Admin --pf
FreeBusy (USER-/CN=RECIPIENTS/CN=ADMINISTRATOR):
        * FreeBusy Last Modification Time:   Tue Oct 21 00:23:00 2008 CEST
        * FreeBusy Publishing Start: Wed Oct  1 00:00:00 2008 CEST 
         *FreeBusy Publishing End:   Mon Dec  1 00:00:00 2008 CET  
        * Busy Events:
                * October 2008:
                        *  30 October 2008 at 9 hours and lasts 2 hours
                * November 2008:
                        *  13 November 2008 at 14 hours and lasts 4 hours
        * Tentative Events:
                * October 2008:
                        *  30 October 2008 at 13 hours and lasts 3 hours and 30 
minutes
                        *  31 October 2008 at 14 hours and lasts 2 hours
    freebusy                 : MAPI_E_SUCCESS (0x0)


We are now trying to create an event starting the 30th October 2008 at 10h00

[EMAIL PROTECTED] trunk]$ ./bin/openchangeclient --sendappointment 
--dtstart="2008-10-30 10:00:00"
Setting default end date
[WARNING]: This start date conflicts with another appointment
    sendappointment          : MAPI_E_INVALID_PARAMETER (0x80070057)

However if we really want to push the appointment, we can still override the 
default behavior:

[EMAIL PROTECTED] trunk]$ ./bin/openchangeclient --sendappointment 
--dtstart="2008-10-30 10:00:00" --force
Setting default end date
[WARNING]: This start date conflicts with another appointment
[WARNING]: This start date conflicts with another appointment
    Unique ID                : 5A27000000000001/168000000000001
    sendappointment          : MAPI_E_SUCCESS (0x0)
==============


Cheers,
Julien.

-- 
Julien Kerihuel
[EMAIL PROTECTED]
OpenChange Project Manager

GPG Fingerprint: 0B55 783D A781 6329 108A  B609 7EF6 FE11 A35F 1F79

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
devel mailing list
devel@openchange.org
http://mailman.openchange.org/listinfo/devel

Reply via email to