On Mon, 2009-03-30 at 18:05 +0200, Paolo Abeni wrote: > hi list, > > I just noticed that event notifications delivered from exchange server > to the client inside a not null transaction are just ignored by > libmapi. I would like to mange such situation adding a call to > ProcessNotification after each call to emsmdb_transaction() (if the > notify_ctx is not null), but the hard part is providing a suitable > 'private_data' pointer. > > This could be solved adding such parameter to the Subscribe() call and > into the 'notifications' struct. Such choice would allow also to > specify different 'private data' when subscribing to different objects > (that IMHO is quite useful), but will break API compatibility. > What do you think ?
Hi Paolo, Sorry for this noticeable delay. I'd just say I've lost a poker game with mother's health which kept me partially away from computers for a few weeks. I think you pointed an interesting issue here. Breaking the notifications API does not sound like a real problem to me. This part of the stack has always been quite experimental and is known to require improvements. The ProcessNotification idea looks reasonable. I also have other ideas/proposals but require a little more time to formalize and review properly. -- 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
