dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.1.0
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Ping timeout: 240 seconds]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
Azure has quit [Ping timeout: 255 seconds]
Azure has joined #cinch
xeviox|afk is now known as xeviox
lmurray_ has joined #cinch
<lmurray_>
Hi, is there any way to ensure that messages are processed in the order that they are received? The order is lost when Cinch dispatches them into separate threads and a simple mutex doesn't work.
<lmurray_>
Looking at the code it doesn't seem possible :(
lmurray has joined #cinch
lmurray_ has quit [Ping timeout: 252 seconds]
ayonix has quit [Ping timeout: 240 seconds]
ayonix has joined #cinch
<dominikh>
lmurray: nope
<lmurray>
:(
leftylink has quit [Ping timeout: 245 seconds]
leftylink has joined #cinch
lmurray_ has joined #cinch
lmurray has quit [Ping timeout: 272 seconds]
lmurray has joined #cinch
lmurray_ has quit [Ping timeout: 252 seconds]
xeviox is now known as xeviox|afk
thews has quit [Remote host closed the connection]
leftylink has quit [Ping timeout: 255 seconds]
thews has joined #cinch
lmurray has quit [Remote host closed the connection]
leftylink has joined #cinch
Azure has quit [Ping timeout: 240 seconds]
Azure has joined #cinch
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]