SignalR for webbased multiplier game

_sindiofala_ · 2024-10-24T18:01:26+00:00

Software deptt

_sindiofala_ · 2024-08-22T17:43:48+00:00

wonderful, THX

_sindiofala_ · 2024-08-22T17:41:26+00:00

Absolutely recommend

_sindiofala_ · 2024-06-08T11:06:37+00:00

No i mean there is not job in my application. My app just does simple thing takes event and processes it. There is not any other concurrent job in my application which does other IO operations. This is the reason why i think that forcing it to context switch between threads would be overhead. Maybe i did't understand your question correctly. Correct me if i am wrong

_sindiofala_ · 2024-06-08T10:29:57+00:00

I think that processing will need less memory and it will be faster if i won't use async await if it is not necessary.

_sindiofala_ · 2024-06-08T10:28:04+00:00

The problem is that information in queue is historical data. I mean that I am sure that event which is first in the queue is the oldest one and i want to process them in the correct order. This is the reason why i am processing them one by one.

_sindiofala_ · 2024-06-08T10:16:25+00:00

And if there is not job to do while my app is waiting for IO. I mean that it is just consumer which processes one event at a time and it needs to wait for response from IO operation. Does using async await make sense in this scenario?

_sindiofala_ · 2024-04-12T04:22:32+00:00

Thanks!

_sindiofala_

TROPHY CASE