WS-Transfer, WAKA and the Web
WS-Transfer can therefore be seen as an underlying protocol-independent version of HTTP, i.e. bringing the capabilities and properties of the Web and HTTP in contexts where HTTP is not used. The use of WS-Transfer is not limited to non-HTTP transports, and can also be used when HTTP is used as a communication tunnel.
Ok, so we all know SOAP jumped the shark a long, long time ago, but I can only assume that WS-Transfer is an early April Fool’s joke. Could somebody please explain to me what sense there is in a half-assed re-implementation of HTTP on top of SOAP?