[Kde-pim] Re: Free-busy integration in KDEPIM - Osnabrück outcome

Thomas McGuire mcguire at kde.org
Wed Apr 6 15:26:30 BST 2011


Hi,

On Tuesday, April 05, 2011 08:19:26 AM Grégory Oestreicher wrote:
> >> Why not, but only the latest message submitted over D-Bus will be kept
> >> in the case that two resources answer with a failure. I assume that you
> >> are only talking about the freebusyRetrieved() call.
> > 
> > Yes, I was talking about the freebusyRetrieved() call. The fact that only
> > the latest message will be kept in memory is an implementation detail of
> > the free/busy manager, and not an API issue, right?
> 
> We can easily store all error messages and provide the API to access them,
> but how are they displayed back to the user? By concatenating them,
> showing them one after the other, saying there's more than one message, or
> otherwise? It's more a usability issue than a coding problem.

We are talking about the API of FreeBusyManager now, right? The API for 
retrieving errors from it can be added later in a binary compatible way, it is 
just important that the FreeBusyProviderBase API is correct, since we can't 
easily change that anymore in a binary compatible way. So as long as 
FreeBusyProviderBase can report the error (which it can now), it should be ok.

Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20110406/767be5d6/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list