> But this seems to only occur _after_ a response has gone back.
> It is as if the server is attempting to gaurantee delivery and getting a
failure when it attempts to do that.
Yes, in your case, the initial transmission of the response would occur over
the backchannel of the original incoming client->server connection.
But then the ACK for this response is not received in a timely fashion,
possibly because of a mismatch between the client-side and server-side
config controlling ACK frequency and the resend interval.
So the server-side attempts to *resend* the original response. Only at this
point the original client->server HTTP connection is no longer available or
suitable for this purpose.
What should have happened is that the wsa:ReplyTo on the original request
was set to a non-anonymous endpoint. Then the initial transmission of the
response would have occurred over a decoupled (or "duplex" in WCF
terminology) server->client connection. If the server-side deems it
necessary to resend this response at a later point in time (due to the
non-receipt of the ACK), it could do so via the same mechanism, i.e. by
re-establishing the server->client connection.
So the whole area of server-initiated resend depends on the original
wsa:ReplyTo being non-anonymous.
Cheers,
Eoghan
2009/3/19 Bryan Kearney <bkearney@redhat.com>
>
> But this seems to only occur _after_ a response has gone back. It is as if
> the server is attempting to gaurantee delivery and getting a failure when it
> attempts to do that.
>
> -- bk
>
|