Hi Bert,
> But given this and our documentation, the only thing about the passed hash
> that we promise are that for each callback type only specific keys are valid
> in the hashtable. All the other values are undefined and it is really upt o
> the api user on how that affects them. In general
The problem here is two folded:
I agree that we *should* properly remove these items from the hash, but we have
had the current behavior since 1.0 even in our previous dav implementation.
But given this and our documentation, the only thing about the passed hash that
we promise are that for each
2 matches
Mail list logo
