> If SRU don't support POST then we can forget about ever having an
> SRU-based update service.
Update is a separate (but companion) service - there is no reason why
Update can't use POST (indeed this is one of the proposed bindings -
POST and SOAP), whilst SRU remains GET only. (some might argue that this
is closer to the REST philosophy).
I could implement SOAP based Update in conjunction with SRU, or POST
based Update in conjunction with SRW if I wanted.