otalk / filetransfer Goto Github PK

the underlying connection could go away in the middle of a transfer (hasn't happened but ...)

This needs to be handled both at the sender and the receiver.

firefox allows querying the amount of data buffered -- this might be useful to adapt the sending strategy for negotiated data channels (which trigger onopen once the sctp/ice connection is up instead of when the other side negotiated the channel)

Can we update the version number and submit a new npm with the new buffering checks?

Is there any reason to hold off?

Thanks!

How do I actually use it, after I have cloned the project?

per some irc-discussion the correct way to reject a negotiated data channel is to create it and close it without hooking up the onmessage thing.