add tests for connection loss, latency, etc.

[derhuerst]

For simulating latency, simulate-network-conditions might be useful.

[ghost]

Could you explain how the two peers connect to each other? It doesn't make sense to me without it either being via localhost or some kind of addressing system.

[derhuerst]

files-sync-stream doesn't care about how peers find and connect to each other. Some examples for possible implementations:

• in Node.js: hardcoded discovery (leader listening on localhost:12345), connection via TCP
• in Node.js: discovery via DNS-SD over mDNS, connection via TCP
• in the browser: discovery via signalhub, connection via WebRTC

The simplest setup is to directly wire two peers together in-process. The tests do it this way.

[ghost]

One basic sample I'm currently working with is the socket.io chat template. Maybe that would be of use.

[derhuerst]

Sure, we can add a examples/socket.io directory which will contain a basic demo of how to use socket.io with files-sync-stream.

[ghost]

What about the project in relation to avion? It looks like it has its own thing going for it over on its page, and it would not be beneficial if it had extra stuff.

[derhuerst]

I don't understand what you're asking, sorry. Can you try to rephrase?

[ghost]

Why add another interface to this project, when the bigger one, avion, already has one of its own?

[derhuerst]

We‘re having a misunderstanding here.

I thought you proposed adding an example this repo on how to use it with socket.io. I don‘t intend to add a UI to this repo.