Tickets :: Comment on [#6658] Allow attribute deletion between SyncML partners

* Your Email Address
* Spam protection	Enter the letters below: . ..___.. ,.__.. . \|\/\| \| \./ [__]\|_/ \| \| \| \| \| \|\| \
Comment	> When receiving set all attributes empty for which we get empty > attributes in the data. This is already done for Turba not sure about > Kronolith. As addition check if we get capabilities from the client > and use them to set attributes empty which the client supports but > have not delivered (this is the second part of the patch). > > > > When sending provide all attributes we know in the data, even empty > ones. Additionally check if we have client capabilities to avoid > sending useless attributes which may get big in size like photo,notes > etc. This is not yet done for Turba/Kronolith. > > > > Would this be an acceptable approach? > > > > From my findings it seams the "CTCaps" are not well supported by most > clients and are stated as "should" not "must" in the SyncML Standard. > >
Attachment
Watch this ticket