Question: Individual annotations vs One large annotation (conceptual riddle for the interested)

Aleksander Machniak machniak at
Tue Oct 11 14:52:37 CEST 2011

On 11.10.2011 14:37, Georg C. F. Greve wrote:

> At the same time your new approach has evident drawbacks in overhead and 
> superfluous use of bandwidth that impact all clients and have given rise to 
> concerns for everyone who spoke up on this issue thus far.


>> No other alternatives have been provided, no blocking objections exist
>> against using one annotation.
> The alternative is to continue the standard best practice that has worked well 
> for Kolab for the past years: One annotation per use case.
> No blocking objections exist against continuing best practice, and no strong 
> argument exists for changing the approach, while the suggested change in 
> standard practice will not only require changing existing applications, thus 
> incur overhead, there is also disadvantages that people are concerned about.
> In such a situation, "if it ain't broken, don't fix it" typically prevails.

I have no strong opinion, but I give my countenance to this position.

Aleksander 'A.L.E.C' Machniak
LAN Management System Developer []
Roundcube Webmail Developer  []
PGP: 19359DC1 @@ GG: 2275252 @@ WWW:

More information about the format mailing list