-
Notifications
You must be signed in to change notification settings - Fork 3
Threading model
Phil edited this page Dec 24, 2017
·
7 revisions
In Vaser, each portal runs its "own" thread.
We have two portals given:
-----------------
| ID 1 | Login |
| ID 2 | System |
-----------------
If you send 10 packets from the 'System' portal and a last packet from the 'Login' portal, Vaser processing all packets in the 'System' portal successively. In the 'Login' portal, Vaser processing packet 11 immediately, at the same time as packet 1 from the 'System' portal.
Send:
----------------------------------------------------------------------------------------
| Login || | pk11 |
| System || pk1 | pk2 | pk3 | pk4 | pk5 | pk6 | pk7 | pk8 | pk9 | pk10 | |
----------------------------------------------------------------------------------------
Time ->
Receive:
---------------------------------------------------------------------------------
| Login || pk11 | |
| System || pk1 | pk2 | pk3 | pk4 | pk5 | pk6 | pk7 | pk8 | pk9 | pk10 |
---------------------------------------------------------------------------------
Time -> ^ processing
Future plans: Add the ability to set the threadingmodel to Portal-, Link- and Packetbased processing.
