Kayak.Http.DataSubject Thread Safety? about kayak HOT 3 CLOSED

This is by design. Kayak is a single threaded event loop.

On Apr 6, 2012, at 4:12, Graham [email protected] wrote:

A quick inspection of Kayak.Http.DataSubject source seems to suggest it has threading issues. For instance, Connect and OnError, which are called by different threads, are written as if channel and error properties were locked together, but they aren't.

Am I missing something here? And if not, is all the Kayak code written in the same way? If so, a wholesale thread safety audit might be in order.

---

Reply to this email directly or view it on GitHub:
#36

from kayak.

In the default implementation of IScheduler, IServer, ISocket, etc (Kayak*), all threading concerns are isolated to KayakScheduler.

from kayak.

Just a bit more info: the only threadsafe public method in Kayak is KayakScheduler.Post, which queues a callback to run on the event loop.

from kayak.