Skip to content

Conversation

lat-murmeldjur
Copy link

This Swarm Improvement Proposal attempts to address enabling browser-based libp2p nodes connectivity to the network and sum up the minimal set of required changes to the protocols involved in connectivity.

@zelig zelig changed the title add ip for communicating websocket addresses add SWIP-65: support communicating with websockets, add ws IP to multiaddress Feb 16, 2025
@zelig zelig added the protocol describes a process every swarm node must implement and adhere to label Feb 16, 2025
@zelig zelig changed the title add SWIP-65: support communicating with websockets, add ws IP to multiaddress add SWIP-23: support communicating with websockets, add ws IP to multiaddress Feb 17, 2025
@zelig zelig changed the title add SWIP-23: support communicating with websockets, add ws IP to multiaddress add SWIP-23: support communication through websockets Feb 17, 2025
@zelig zelig changed the title add SWIP-23: support communication through websockets add SWIP-24: support communication through websockets Feb 18, 2025
@zelig zelig changed the title add SWIP-24: support communication through websockets SWIP-24: support communication through websockets Feb 18, 2025
@lat-murmeldjur
Copy link
Author

Update: With ports consistently reused between tcp and websocket underlays we can achieve derivation of websocket underlays from gossiped tcp underlays, that enables hive protocol to remain intact

@lat-murmeldjur
Copy link
Author

Update 2: It seems port reuse has some issues that make it less feasible as a long term solution, with requests hanging for 10 seconds periodically. Reopening this as a mid-term solution proposal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol describes a process every swarm node must implement and adhere to
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants