Add some more discovery mechanisms #38

Open
wants to merge 2 commits into
from

Conversation

Projects
None yet
2 participants
@tdfischer

This adds DNS-SD and host-meta discovery mechanisms to the spec.

@slopjong

This comment has been minimized.

Show comment Hide comment
@slopjong

slopjong Jan 6, 2013

How would this work with DNS-SD? I've never worked much with DNS stuff. How much effort would (more or less) be required to get it done?

Are you sure that it has much value? In OpenSpaceLint everyone can add a space and if the auto validator is done (one time) the spaces get reports if something is broken. With a simple backlink to the github issues they can request a change.

I think the static way is the way to make it as simple as possible but not simpler.

How would this work with DNS-SD? I've never worked much with DNS stuff. How much effort would (more or less) be required to get it done?

Are you sure that it has much value? In OpenSpaceLint everyone can add a space and if the auto validator is done (one time) the spaces get reports if something is broken. With a simple backlink to the github issues they can request a change.

I think the static way is the way to make it as simple as possible but not simpler.

This comment has been minimized.

Show comment Hide comment
@tdfischer

tdfischer Jan 6, 2013

Owner

If a sysadmin can configure the local DNS to support DNS-SD, or configure avahi/ zeroconf/etc, a mobile device can automatically discover the current space's information.

Having it in the spec has no impact on the website or JSON, so I don't see a reason it shouldn't be documented. We use this for some of our kiosk software at SYNHAK. Should another space use the software, DNS-SD would be used to find status.json to configure itself appropriately and automatically.

Owner

tdfischer replied Jan 6, 2013

If a sysadmin can configure the local DNS to support DNS-SD, or configure avahi/ zeroconf/etc, a mobile device can automatically discover the current space's information.

Having it in the spec has no impact on the website or JSON, so I don't see a reason it shouldn't be documented. We use this for some of our kiosk software at SYNHAK. Should another space use the software, DNS-SD would be used to find status.json to configure itself appropriately and automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment