B4J Question Multiple classes with async streams communications.

It will work. Each connection / AsyncStream will work mostly independently. The NewData events are raised on the main thread.

With that said - I don't recommend building complex solutions with AsyncStreams unless you have no choice. Better to use MQTT or jServer.

Example of a server built with AsyncStreams (this is mandatory here as it implements a specific protocol): https://www.b4x.com/android/forum/t...d-with-socket-and-asyncstreams.74320/#content

Erel said:

It will work. Each connection / AsyncStream will work mostly independently. The NewData events are raised on the main thread.

With that said - I don't recommend building complex solutions with AsyncStreams unless you have no choice. Better to use MQTT or jServer.

Click to expand...

You are right. I did not mention it. I am using a JServer with this array located in a background worker class. So according to what you said I can conclude that everything will run in the background worker thread. Right?

This is an important point as jServer solutions have a different threading model.
Start here: https://www.b4x.com/android/forum/t...ads-sessions-and-server-events.39969/#content

You need to provide more information about your architecture. How are you creating the classes instances? How are you interacting with those instances?

Erel said:

This is an important point as jServer solutions have a different threading model.
Start here: https://www.b4x.com/android/forum/t...ads-sessions-and-server-events.39969/#content

Click to expand...

Thanks for answering. This is an extremely interesting post. I have a question for this: If we call the method f.e. ChatShared.Init without CallSubDelayed but directly from a background Worker thread, since ChatShared is a shared module, where does the code of "Init sub" run? In the main thread or in the worker thread?

Erel said:

You need to provide more information about your architecture. How are you creating the classes instances? How are you interacting with those instances?

Click to expand...

Everything (all the functionality - f.e. the async_newdata sub, async_error etc.) runs in the async stream class. I just create a new class for the worker and initialize the async stream classes as an array in it. The worker has now also active code for managing the newdata events with callsub from the classes but I will move everything inside the async stream classes so do not take this under notice. What attitude do you think should I expect from this?

hatzisn said:

Thanks for answering. This is an extremely interesting post. I have a question for this: If we call the method f.e. ChatShared.Init without CallSubDelayed but directly from a background Worker thread, since ChatShared is a shared module, where does the code of "Init sub" run? In the main thread or in the worker thread?

Click to expand...

When you directly call a method, it always run on the same thread. It is only when you call it with CallSubDelayed that the call can be transferred to a different thread.

If all class instances are created from the worker class instance then they will be "owned" by the worker thread.

Note that you can always verify it by logging the value of Main.srvr.CurrentThreadIndex.
And make sure to test it in release mode as in debug mode everything runs on the main thread.