On Mon, 2009-03-30 at 17:11 +0200, Paolo Abeni wrote: > hello, > > I stuck into another NotificationData parsing issue, this time for > SearchMessageModifiedNotification event. > > Checking the "Core Notifications Protocol Specification", there are a > few issue with current idl code for parsing event notification, which > the attached patch should fix (it include the patch I posted > previously, since it seams to match the specification). > > According to the protocol specification a value of 0xffff for the > 'TagCount' field must be interpreted as 0 (no tags follow). How can be > specified this behavior into the idl ?
Hi Paolo, Sorry I couldn't reply your emails sooner. I'll give a closer look at you Subscribe + Notification protocol + IDL changes proposal this afternoon and get back to you as long as I finish reviewing each of your emails. For the TagCount, yeah we can add this specific behavior in the IDL - and I'll do it right after I review your patch. I think we should probably introduce a mapitest module about these notifications so we ensure everything is working properly and we not break anymore along further commits. Cheers, Julien. -- Julien Kerihuel [email protected] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
