Ok, I see. It's as much an exercise in application level interop as it
is SOAP interop. So for conveying the link URL to the client, what
do you consider best:
1) use HTTP header
2) use SOAP extension (header block)
3) use response message in body
?? (I'm torn between 2 and 3)
> That's why I suggested a "create" operation which returns a hypertext
> link to the new resource in the response.
> > If this is not possible, then the prerequisite must be
> > the development of a scheme for doing this, which SOAP 1.2
> explicitly does
> > not provide. Of course there's been a lot of discussion on this
> subject on
> > various lists, but it's been inconclusive so far. If found
> necessary, does
> > the development of such a scheme fall within the scope of the
> > testing effort?
> We can leave that part to the hoi polloi. From what I understand,
> the actual intent is enable soap toolkits to retrieve SOAP responses
> from arbitrary (i.e., opaque) URLs using HTTP GET.
> - Sam Ruby