Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support/document how to use with Physical Web #84

Open
jonnor opened this issue Feb 9, 2017 · 3 comments
Open

Support/document how to use with Physical Web #84

jonnor opened this issue Feb 9, 2017 · 3 comments

Comments

@jonnor
Copy link
Member

jonnor commented Feb 9, 2017

For instance to broadcast the Flowhub live-url to connect to the system. Probably using their mDNS support, as msgflo broker typically runs on Linux which can have Avahi etc.

@jonnor
Copy link
Member Author

jonnor commented Feb 9, 2017

Seems first they need to fix google/physical-web#893

@bergie
Copy link
Member

bergie commented Feb 10, 2017

The other option is using Bluetooth. Should be reasonably easy to set up if running the MsgFlo coordinator on Raspberry Pi (like we will with https://github.com/c-base/c-flo):

https://medium.com/@urish/exploring-the-physical-web-without-buying-beacons-efae51e36c2e#.d4xwmmkxr

@bergie
Copy link
Member

bergie commented Jun 3, 2017

It seems one option would be UPnP/SSDP version of Physical Web, which is reasonably straightforward to support with Node.js without additional hardware.

However, see the discussion in google/physical-web#619

Right now it seems the SSDP discovery mechanism only works in the Physical Web Android app, not in Chrome.

Additionally, Physical Web requires HTTPS URLs, which will not work until we add wss support to MsgFlo coordinator. Related to noflo/noflo-ui#433

By sending a HTTPS URL, the runtime was found by the Android app:
screenshot_20170603-204046

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

No branches or pull requests

2 participants