[Cosmo-dev] Flushing the properties when there is a second put

[Vinubalaji Gopal]

On Thu, 2006-08-17 at 18:49 -0700, Brian Moseley wrote: 
> no, let's not do that. instead let's just remove the properties that
> are no longer part of the icalendar/vcard object

Done, was thinking about the performance implications and it was a bit
tricky to implement (Mainly because I am using multi-valued properties
for the properties in vCard)

I feel that a commit and rollback model will be good for this case with
an added benefit of better performance. Right now I get all the
properties, delete it and then store the new value, if any. You could
give me a feedback while you start with the code review - the complete
carddav implementation is up to date in my subversion sandbox.


There are lot of other places that the performance may (or will) suck
and I don't have an option other than writing a vcard parser sometime if
it becomes a real problem.