W3C home > Mailing lists > Public > www-xkms@w3.org > January 2005


From: Berin Lautenbach <berin@wingsofhermes.org>
Date: Mon, 17 Jan 2005 19:10:53 +1100
Message-ID: <41EB730D.4050801@wingsofhermes.org>
To: "www-xkms@w3.org" <www-xkms@w3.org>


I've had my somewhat flaky server hanging on me fairly regularly, and I 
just tracked the problem down.

StatusRequest processing is fairly ill-defined in the spec.  I 
originally assumed that the OriginalRequestId attribute should be used 
to lookup the original request.  Someone has been sending me a 
StatusRequest without the OriginalRequestId set, but with ResponseId 
set.  My server wasn't properly checking that everything it needed was 
there, so it got unhappy.  I have now updated to also lookup based on 
ResponseId if the OriginalRequestId is not there.

However I'm curious as to which is correct, particularly given 
interactions between two-phase and asynchronous.  I.e. OriginalRequestId 
is set to InitialRequest/Phase 1 for everything later - which confuses 
any async lookups based on OriginalRequestId.  In which case - if the 
semantics of OriginalRequestId change depending on mix of two phase and 
async, why not use OriginalRequestId for one and REsponseId for the other?

Does all of that make sense, or have I completely missed the point 
somewhere along the line?

Received on Monday, 17 January 2005 08:11:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:43 UTC