Re: [w3ctag/design-reviews] The web platform needs a service discovery mechanism (#240)

Just to be clear, the part that this touches on is the hardcoded part in section 3 in the OSP spec. I’m not particularly thrilled about exposing mDNS (with all it’s quirks) over the web platform, but it is indeed a viable option since it has extremely wide adoption. (We previously attempted this in the past with NFD spec, but I don’t consider that a success.) What we would like to see come out of the discussion is the following:

1) A common API interface/pattern for designing service discover-like features (e.g. local network and bluetooth might be examples where we can have a similar API pattern), sort of like what we did with streams
2) A mechanism for exposing/discovering network services (e.g. query default dns resolver, mDNS, etc.)

Do note that this is not a place where we are gathering proposals, it’s more of a architectural concern issue where we want to not do N inconsistent API patterns, and end up with a pile of regret later.

We mentioned media because it feels like the most immediately use case which can benefit from this - as a immediate example, Plex does a lot of interesting (en_UK interesting) things to work around this not being available; so there is a clear need.

Should we setup a separate call to discuss if this is worth a plenary breakout during TPAC later this year?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/240#issuecomment-495112332