"Protocol layer" cleanup

[tobixen]

As part of the "async sans-I/O-pattern", claude made a "protocol layer", bare functions under caldav/protocol/xml*.py

However, we still have XML parsing logic in the Response class - and now we even have some overlapping code.

Does it make sense to have the "protocol layer"? Could we not have the response class do all the xml parsing?

In any case, the duplicated code should be deduplicated and XML parsing should be done one and only one place.

[tobixen]

Same goes with the "operations layer". Also cruft from a mostly failed attempt on following the sans-io design pattern, it should be cleaned up and rethought.

Claude seems to strongly suggest that I do an "async first, generated sync code"-pattern. My only objection is that I do not like generated code. I've always thought that when one has to generate code, it basically means the programming language is not good enough, it is not allowing the programmer to express himself efficiently enough.