Closed GoogleCodeExporter closed 9 years ago
User code processing received messages on the library thread is bound to create
difficult-to-find bugs. There are many other ways to retrieve messages better
suited to applications without a synchronization context. However, I just
checked in revision 253 which contains a better exception than a null ref
exception.
Original comment by lidg...@gmail.com
on 18 Jul 2011 at 9:11
Ok agreed. I was looking for asynchronous notification of received messages
without using any polling loops and this appears to be it in this library. I
have not checked current code but I think and InputQueue<T> would be a
reasonable class for that which is what I am piping the results of this event
through (to avoid locking the library thread). (Search WCF samples for that
class if interested).
Original comment by abbott.t...@gmail.com
on 18 Jul 2011 at 10:01
Original issue reported on code.google.com by
abbott.t...@gmail.com
on 11 Jul 2011 at 5:47