| … | |
… | |
| 417 | in each iteration of the event loop (This behaviour is called |
417 | in each iteration of the event loop (This behaviour is called |
| 418 | level-triggering because you keep receiving events as long as the |
418 | level-triggering because you keep receiving events as long as the |
| 419 | condition persists. Remember you can stop the watcher if you don't want to |
419 | condition persists. Remember you can stop the watcher if you don't want to |
| 420 | act on the event and neither want to receive future events). |
420 | act on the event and neither want to receive future events). |
| 421 | |
421 | |
| 422 | In general you can register as many read and/or write event watchers oer |
422 | In general you can register as many read and/or write event watchers per |
| 423 | fd as you want (as long as you don't confuse yourself). Setting all file |
423 | fd as you want (as long as you don't confuse yourself). Setting all file |
| 424 | descriptors to non-blocking mode is also usually a good idea (but not |
424 | descriptors to non-blocking mode is also usually a good idea (but not |
| 425 | required if you know what you are doing). |
425 | required if you know what you are doing). |
| 426 | |
426 | |
| 427 | You have to be careful with dup'ed file descriptors, though. Some backends |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
