On 25-Feb-06, at 10:05 AM, robert yates wrote:
Also, does it not make sense to have the verify step be a REST style xml web service vs. this current form POST. XML seems much better suited to these character encoding issues than "application/ x-www-form-urlencoded".
We had a fair amount of discussion on this. We chose POST although it is less elegant then a REST style call because we did not see any functional advantage, and for the following implementation advantages;
1) Currently, the HS is not having to parse any HTML or XML, and the MS is only generating pretty standard HTML. A little more complexity in adding XML to the base.
2) The HS is already getting POSTs on the Homesite-URL for the other messages. By having the verify message be another POST in the same format, it was thought it would be easier to implement a HS. The unique ID for the HS is the Homesite-URL, as it is in the Persona document and is where the MS sends all requests, either directly or indirectly.
Who knows whether the libraries for Ruby, Python, Java et al will be consistent with how they perform their character encoding.
I am pretty sure they are consistent. _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
