Looking into WCF

Guys, good work. But I am missing something. I am missing the direct implementation details, that developers should use to "process" those cards. The documentation is scattered and is by no means complete. I am talking about: how to process tokens (Garret's TokenProcessor is good), what should the application store to identity user (Vibro explains on his blog), what happens when the server certificate changes (expires, so the administrator installs a new one), etc, etc. If there is a document, describing all those aspect, it is very well hidden. I would expect this document to be on the first page of cardspace.netfx3.com. What are the best practices for enabling mixed login support? (like intermediate pages with javascript that triggers the Cardspaced UI on the client). It is also very good news that you are supporting other platforms as well, but it would be good to support (and *document*) your platform as well. :) . Regards, Miha.

See my comments under "Horrible Human Engineering" at <a href="http://ejnorman.blogspot.com">http://ejnorman.blogspot.com</a>