- From: Michał 'rysiek' Woźniak <rysiek@fwioo.pl>
- Date: Tue, 11 Jun 2013 16:32:26 +0200
- To: public-fedsocweb@w3.org
- Message-Id: <201306111632.26553.rysiek@fwioo.pl>
Dnia wtorek, 11 czerwca 2013 o 12:55:11 Simon Tennant napisał(a): > Hi Melvin > > There's two problems to be solved. > > 1. How to find the responsible server for a domain's social network. (Which > server runs the social network functions for EXAMPLE.COM?) > 2. How clients find their API endpoint (user@EXAMPLE.COM is trying to > log-in on a new mobile-social-app, what API endpoint do I use for > EXAMPLE.COM) > > The first problem is solved using SRV records or webfinger or whatever > > The second problem is solved using DNS-SD. The lookup is "magically" > simple. In buddycloud's case the mobile client will do the following query: > > dig -t TXT _buddycloud-api._tcp.EXAMPLE.COM. +short > > and get back the following easily parseable content: > > "v=1.0" "host=demo.buddycloud.org" "protocol=https" "path=/api" "port=443" > > To make this work you just need to add something like the following to your > zone file. > _buddycloud-api._tcp.EXAMPLE.COM. IN TXT "v=1.0" "host= > buddycloud.EXAMPLE.COM" "protocol=https" "path=/api" "port=443" > > So for your app, just change _buddycloud-api to whatever you would > like (and if you are creating new protocols, be nice and register them with > IANA). +1 That would be the best solution, but no social network software I know of implements it. Instead, webfinger is being used. :/ -- Pozdrawiam Michał "rysiek" Woźniak Fundacja Wolnego i Otwartego Oprogramowania
Received on Tuesday, 11 June 2013 14:54:58 UTC