book-exploring-async-basics
book-exploring-async-basics copied to clipboard
[Translation] 8_6_io_eventqueue.md
One area we're taking shortcuts on all the way here is security.
It means that security is what have been ignored in the previous chapters.
There are several ways in which we could register interest in more events than occur, and thereby allocating memory that is just held in the buffers.
So if the user registers a lot of events that would not happend or take a long time to happen then a lot of allocating memory is just held by OS and could not be used by user, which may finally lead to OOM?
It means that security is what have been ignored in the previous chapters
yes
So if the user registers a lot of events that would not happend or take a long time to happen then a lot of allocating memory is just held by OS and could not be used by user, which may finally lead to OOM?
Yeah, that's spot on. That's why you should limit the amount of outstanding buffers on completion based systems since someone could exploit this.
If someone were to build a public facing server out of this, ...
What is this here referring to, secure or the example we are exploring?
Here is a more precise sentence:
If someone were to build a public facing server based on our the code in our example...