Hey,

> Couldn't an alternative to be deprecate and get rid of wbsetclaim as you can do
> everything it can do and more through wbeditentity with little more knowledge of
> the serialization format..

If so, we should get rid of *all* the editing modules

Damn, seems I was to late to have addshore assassinated, and now this discussion is starting again. The end is near!

I think when we last discussed this, we decided to keep the more specific modules because they are better "verbs" in the REST sense.

AFAIK this was because we want fine grained actions and interfaces for them, not because of similarity to HTTP vebs. (I see what you are getting at, though think HTTP verbs are a bad example here.)

They could
perhaps be re-implemented as a think layer on top of editentity. Since all of
them use ChangeOps by now, we wouldn't gain terribly much, i guess.

Agree, there should not be much of a difference. And if there is, the solution lies with fixing the code, not changing the web API.

At the same time I agree with addshore that there is some cost in maintaining this code, though if this little glue code is all that is needed to provide a feature that is actually in demand, I think we can all agree on it being well worth the maintenance.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--