… the top level now.
… spec, but is consistent with what providers in the wild do and is the only way this can work without breaking backward compatibility.
… in the "common" package.
…sn't actually do anything yet. One problem with this design right now is that there's no support for extension response fields to be signed. I'll work on that later.
…it so that future versions of ::Server can use them: * Net::OpenID::IndirectMessage can be used to make Server support extensions in the same way that Consumer does. * Net::OpenID::Yadis can be used by Server to implement RP endpoint discovery. * Net::OpenID::URIFetch is a dependency of Net::OpenID::Yadis.
…RD direct input
Easier to remember that versions >= 1 support OpenID 2 rather than versions > 0.14