Subject: object reference not set in ClientSocket.EndSend
Hi,
In my project there is requirement to have multiple MUC rooms. Each room signifies a data that comes from a equipment.
There is a component (called Writer) that reads the data from multiple equipments and writes to the data to the respective rooms from multiple threads. There are client components that listen to the data from mostly all the room.
I've encountered few problems - the significant one is the object reference exception in ClientSocket.EndSend method.
The other problems I've received are in the MessageGrabber when the client component registers (from multiple threads) a callback, there is exception saying the enumeration is modified in another thread. I solved it by adding a lock in the registration code. I suggest that the MessageGrabber.Add and Remove methods be locked...
Is the library production ready? I see a lot of Console.WriteLine in the library code... Should I wait for a newer version?
In my project there is requirement to have multiple MUC rooms. Each room signifies a data that comes from a equipment.
There is a component (called Writer) that reads the data from multiple equipments and writes to the data to the respective rooms from multiple threads. There are client components that listen to the data from mostly all the room.
I've encountered few problems - the significant one is the object reference exception in ClientSocket.EndSend method.
The other problems I've received are in the MessageGrabber when the client component registers (from multiple threads) a callback, there is exception saying the enumeration is modified in another thread. I solved it by adding a lock in the registration code. I suggest that the MessageGrabber.Add and Remove methods be locked...
Is the library production ready? I see a lot of Console.WriteLine in the library code... Should I wait for a newer version?
svenk
Show profile
Link to this post
ToPost.zip 59.2 kBytes