Changeset 57 in code for trunk/upstream.go

Timestamp:

Feb 17, 2020, 2:46:29 PM (5 years ago)

Author:

contact

Message:

Fix issues related to Ring

• RingConsumer is now used directly in the goroutine responsible for writing downstream messages. This allows the ring buffer not to be consumed on write error.
• RingConsumer now has a channel attached. This allows PRIVMSG messages to always use RingConsumer, instead of also directly pushing messages to all downstream connections.
• Multiple clients with the same history name are now supported.
• Ring is now protected by a mutex

File:

• trunk/upstream.go (modified) (3 diffs)

trunk/upstream.go

@@ -45 +45 @@
         modes      modeSet
         channels   map[string]*upstreamChannel
+        history    map[string]uint64
 }
 
@@ -67 +68 @@
                 ring:     NewRing(u.srv.RingCap),
                 channels: make(map[string]*upstreamChannel),
+                history:  make(map[string]uint64),
         }
 
@@ -306 +308 @@
         case "PRIVMSG":
                 uc.ring.Produce(msg)
-                uc.user.forEachDownstream(func(dc *downstreamConn) {
-                        dc.SendMessage(msg)
-                })
         case irc.RPL_YOURHOST, irc.RPL_CREATED:
                 // Ignore