...
Supporting changes would need to be made to HttpOperationInOut and WSDLParser (to support the value) and DisseminationService.assembleDissemination (to build the URL). This appears to be a less dramatic change than some others, and would offer a way to support multiple-value input parms without WSDL2 support. Along with some of the other proposed features, a key component is probably refactoring DisseminationService into an interface, with supporting implementations for different operation types.
Rudimentary support for HTTP POST
If the ServiceMapper class is refactored to allow multiple bindings, it opens the door to supporting additional http verbs. This would require some additional refactoring of the binding classes to key on verb, and elaborating org.fcrepo.common.http.WebClient to support POST. This is only considering support for the verb (for example, to skirt URL length restrictions on bound services), not its role in REST or the requirement of idempotency.
Deliver Composed WSDL for Object Disseminations
...
Necessary to support SOAP with attachments or MTOM, allows for some transport efficiency of b64 encoding.
Allow SDefs to Specify SOAP Services
...
4. Strategies for services as different types of endpoints
WSDL-2 Support in Service Definitions and/or Deployments
Pros: Better language for multiple verbs; better support for serialization of multiply-valued parts into URLs for GET requests or XML for POST; request header support; multipart/form-data support; supported by Axis2
...
It might very well be flexible enough to model a known external API, so there's a possible path of defining WSDL-2 SDeps, and having them proxied by a simpler WSDL-1.1 SDef
See also this IBM developerWorks article on REST and WSDL-2.
FCREPO-500: Writeable disseminators; POST support
...