ff3e63da8d
- when testing streams to WSS client, I caused tunnel.js to abort in xfer. - this caused a panic in go. - found that connection was reaped and garbage collected during send routines. - placed synchronize around a connection states. - moved connection creation into connection table. - allowed connections to hang around while in a false state… - will have a go routine remove them after some idle time and connections being false. |
||
|---|---|---|
| .. | ||
| packer.go | ||
| packer_data.go | ||
| packer_header.go | ||
| setup.go | ||