Skip creating the named pipe on the client if we're using http signaling

* Blocks waiting on the open for write (`cat > signal`), at least for me.
This commit is contained in:
Arlo Breault 2016-01-19 21:44:23 -08:00
parent 62e6704d1f
commit 0abb3bd856

View file

@ -331,19 +331,21 @@ func main() {
log.Println("starting") log.Println("starting")
// This FIFO receives signaling messages. if offerURL == "" {
err = syscall.Mkfifo("signal", 0600) // This FIFO receives signaling messages.
if err != nil { err = syscall.Mkfifo("signal", 0600)
if err.(syscall.Errno) != syscall.EEXIST { if err != nil {
if err.(syscall.Errno) != syscall.EEXIST {
log.Fatal(err)
}
}
signalFile, err := os.OpenFile("signal", os.O_RDONLY, 0600)
if err != nil {
log.Fatal(err) log.Fatal(err)
} }
defer signalFile.Close()
go readSignalingMessages(signalFile)
} }
signalFile, err := os.OpenFile("signal", os.O_RDONLY, 0600)
if err != nil {
log.Fatal(err)
}
defer signalFile.Close()
go readSignalingMessages(signalFile)
webrtc.SetLoggingVerbosity(1) webrtc.SetLoggingVerbosity(1)