Go to file
Evan Prodromou 03677f1a81 better handling of XRDS files
Our generated XRDS files contain 3 XRD elements: one for OAuth, one
for OMB, and one to point to the other two. Auth_Yadis only gives us
the last one, so we have to use it to find the other two, and then
extract service URLs from them.

Kind of fragile code, probably won't hold up under complicated
topologies, and won't work at all if the XRDs are in another XRDS
container. I tried to use XRDS filtering to get the top-priority
version of XRDs, services, and URIs, but Laconica's output doesn't use
any of that stuff and I don't particularly want to test it.

darcs-hash:20080602174249-84dde-b7ffdf7f21afb5b734def70530fc305689da471d.gz
2008-06-02 13:42:49 -04:00
actions better handling of XRDS files 2008-06-02 13:42:49 -04:00
classes server-side storage model 2008-05-27 16:07:21 -04:00
db server-side storage model 2008-05-27 16:07:21 -04:00
doc remotesubscribe form 2008-05-30 13:43:10 -04:00
lib better handling of XRDS files 2008-06-02 13:42:49 -04:00
theme/default default avatars 2008-05-21 07:46:24 -04:00
config.php.sample trim whitespace 2008-05-20 15:14:12 -04:00
COPYING license block for source code 2008-05-14 15:26:48 -04:00
dataobject.ini add data objects 2008-05-07 13:15:42 -04:00
index.php trim whitespace 2008-05-20 15:14:12 -04:00