Re: [apps-discuss] Aggregated service discovery

[Mark Nottingham <[e-mail]>]

On 23/05/2012, at 10:55 PM, Cyrus Daboo wrote:

> Hi Mark,
> 
> --On May 23, 2012 4:29:24 PM +1000 Mark Nottingham <[e-mail]> wrote:
> 
>> If they're HTTP -
>> <https://datatracker.ietf.org/doc/draft-nottingham-json-home/>
> 
> Of course we do want service discovery for non-HTTP protocols, LDAP, IMAP, Submission, POP3, XMPP etc. Now I could almost imagine having non-http resource URIs in the json-home document for these other protocols, but I think that would be over stepping the intent of json-home.

As long as the relationship is expressed as a well-defined link relation, I don't see a problem. Of course, some of the HTTP-specific bits are going to be irrelevant, but there isn't anything requiring their use (maybe I should call it "http-hint"?).


>> Not yet convinced that well-known is needed for this yet; it's
>> effectively substituting a hostname for a full URL.
> 
> Not sure what you mean by that. Obviously it is important to have just one jumping off point for this.


1) What's the use case driving having ONE location for it? Some of the advice in .well-known is to lump things that share a use case into a single URL, but to avoid having "kitchen sink" well-knowns, because they become unwieldy. Is there a strong use case for someone discovering ALL of the various (and often totally unrelated) services a site offers in one request?

2) Even if it's so, the question I'm asking is why that ONE identifier is a hostname instead of a URL. Are there some hidden UI requirements at work here, perhaps?

Cheers,

--
Mark Nottingham   http://www.mnot.net/