Skip to content
This repository has been archived by the owner on Jan 20, 2023. It is now read-only.

Expose http-based bootstraps/transports on the gateway #4

Open
ghost opened this issue Nov 3, 2016 · 0 comments
Open

Expose http-based bootstraps/transports on the gateway #4

ghost opened this issue Nov 3, 2016 · 0 comments
Labels
kind/enhancement A net-new feature or an improvement to an existing feature

Comments

@ghost
Copy link

ghost commented Nov 3, 2016

This will be useful for serving js-ipfs out of the gateway, and having working peering right away, without having to set up anything. For example the websockets transport would live at :8080/ws, and anything loaded through that gateway could access it.

@whyrusleeping @diasdavid Does this sound relevant to js/go interop? Maybe I'm missing something. I was thinking along the lines of same-origin policy.
@ghost ghost added the kind/enhancement A net-new feature or an improvement to an existing feature label Nov 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/enhancement A net-new feature or an improvement to an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants