Editing 278: Black Hat Support
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 15: | Line 15: | ||
Finally, Black Hat asks the client on the phone to "bear with him" and suggests that the client should use a highly obsolete mechanism to look for the answer to his problem, namely AOL keywords. {{w|AOL}} is well known for producing one of the earlier {{w|online communities}} and has since fallen largely out of favor. The client hangs up the phone. | Finally, Black Hat asks the client on the phone to "bear with him" and suggests that the client should use a highly obsolete mechanism to look for the answer to his problem, namely AOL keywords. {{w|AOL}} is well known for producing one of the earlier {{w|online communities}} and has since fallen largely out of favor. The client hangs up the phone. | ||
| β | The title text mentions the function [http://linux.die.net/man/2/select select()] | + | The title text mentions the function [http://linux.die.net/man/2/select select()] which allows you to write asynchronous IO access routines by checking if it is ready to be read/written to at a specific moment. This is different than a threaded model in that it can happen in a single thread. The danger of such programming is that if you do not coordinate the reader/writer properly you can create a dead lock which can result in the consumption of a lot of resources. |
==Transcript== | ==Transcript== | ||
