DIME interop - RPC endpoint up

A live endpoint is now available for DIME testing involving SOAP RPC =
payloads:

http://www.whitemesa.net/dimetest/rpc

This implements a SOAP RPC/DIME test interface described here:

http://www.whitemesa.net/wsdl/dime_rpc.wsdl

It consists of two methods, echoBase64 and echoHexBinary. At present the =
WSDL incorporates none of the extensions described in the "WSDL =
extension for SOAP in DIME" spec. As the WM SOAP server dispatches on =
the basis of the media type of the HTTP content, the same endpoint will =
also handle SOAP messages for these operations that are not DIME =
packaged, and respond in kind. At present I plan to limit attachment =
support to the binary types. Note that the data is not actually hex or =
base64 encoded when sent as a DIME attachment.

SOAP RPC messages must be encapsulated per the "Encapsulating SOAP in =
DIME" draft. The server closes connections that have been open longer =
than 60 seconds, effectively limiting the DIME package size.
At present id/href values must be absolute URIs.

Here's an example (primary payloads only in trace log):

TIME: 06/May/2002:05:29:09
SOAP URI: /dimetest/rpc
Method Handler ProgID: Interopsvcdime.interoprpc
SOAPAction: "http://soapinterop.org/"
Actor URI: ""
Next Hop URL: ""

REQUEST MESSAGE:

<?xml version=3D"1.0" encoding=3D"UTF-8"?><SOAP-ENV:Envelope =
xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Bo=
dy><m:echoHexBinary =
SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/" =
xmlns:m=3D"http://soapinterop.org/"><inputHexBinary =
href=3D"uuid:C25C0E63-2D1F-4D19-8C3D-56C265158FEB" =
/></m:echoHexBinary></SOAP-ENV:Body></SOAP-ENV:Envelope>

RESPONSE MESSAGE:

<?xml version=3D"1.0" encoding=3D"UTF-8"?><SOAP-ENV:Envelope =
xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Bo=
dy><m:echoHexBinaryResponse =
SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/" =
xmlns:m=3D"http://soapinterop.org/"><return =
href=3D"uuid:61B5B59F-30BD-414A-A2FC-928D3074B834" =
/></m:echoHexBinaryResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

Request payloads may be chunked or unchunked, but response payloads will =
be sent chunked with a record size of 4096 octets. HTTP 1.0 is used at =
present.

RC