Is wclSyncClient thread-safe?

[luigidallavalle]

Hi All,
    I have an windows form application that communicates (reads\writes) with a device through SPP.
The typical communication cycle is:
1 the application sends a command
2 the application wait for a response, which is always and quickly sent back by the device.

I have a wclSyncClient which is created in the UI thread at the application start (the channel is opened at the same time), then it's used in both the UI thread by some event handler that responds to user actions, and in other background threads. Every access to the client is synchronized through locks.
What happens is that, sometimes, in the background threads, the Read method cannot receive anything, I also have a retry policy, Read is called several times, always with 0 byte read.
After that, when the users triggers a command by using the UI, all the data I was expecting are now received by a the first Read attempt.

I noticed that the odd behaviour occours mostly when the background operation is performed immediatly next to a UI triggered one.

Because of that I suspect that the wclSyncClient is not thread-safe, what are your thoughts?

Thanks in advance,
Luigi

[Mike Petrichenko]

Hello,

The wclSyncClient must be used in the same thread it is created/connected. Also if you use it in non-guid thread the thread must have a message loop.

For your case I recomend to use asynchronous wclClient instead of wclSyncClient.

[luigidallavalle]

Thanks a lot for the quick response!

[luigidallavalle]

I have the same problem using wclClient too, but I'm not sure if I'm doing everything in the right way:
in the main thread, the wclClient is created and onData event handler is assigned.

When waiting for data from a background thread what appens is that the onData event is never triggered, it is fired when the control passes to the main thread.
is it the correct behaviour?

If it is, what I need to do is to subscribe \ unsubscribe che event handler every time I need to wait for data to come, in thaw way I'll be sure that che event subscription is made in the same thread which sends the data, is it correct?

thanks Mike

[Mike Petrichenko]

with wclClient you do not need any background thread as it is asynchronouse.

If you want to use it in threads then your thread must have a message loop and the wclClient object must be created and opened in thread where it is used.