On 11-Feb-06, at 3:17 PM, Eric Rescorla wrote:
Use of Javascript
Section 5.10.2.1 reads:
The Membersite sends a fetch-request message to the Homesite
through
the User's client via a redirected HTTP POST to their Homesite
Endpoint URL using JavaScript to autosubmit the form.
I appreciate the rationale for this: you want things to work with
dumb clients but given that Javascript isn't any kind of IETF
standard--it's hard to see how we could require it in an IETF
standard. ECMASCript, perhaps. Even then, specifying this kind
of implementation detail is the kind of thing that IETF typically
stays out of. I appreciate that this is also a wire protocol issue,
but given that there's no specification of the exact JavaScript
incantation, it's not clear it makes sense to specify only
the language.
I've changed the wording so that auto submission is a 'should',
and that using ECMAScript is a 'could'.
Thanks
John
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
