Quote:
Originally Posted by Inline
Solutions implemented before, usually achieved only second requirement or just basically nothing. They used raw sockets and blocked the main thread for the IO.
To solve blocking problem requests were dispatched to another thread (See for SQL_ThreadQuery for example). This approach has several problems. One of them is the difficulty on concurrent and safe programming in C++. To speed up things, thread pool should be written. With bad dependency management... This is just a mess!
....
Rust has many libraries dedicated to high-performance HTTP(s) requests, implemented (at the lowest level) using non-blocking sockets. It is extremely easy to write something in Rust, which is otherwise nearly impossible in C++.
|
I am confused
There are two types of sockets, IIRC, Blocking and non-blocking.
If this module is using non-blocking sockets, how it different from many already existing non-blocking modules (for sockets) on this community ?
__________________