Mercurial > luaevent-prosody / file comparison
comparison: doc/modules/luaevent.core.mdwn
doc/modules/luaevent.core.mdwn
- changeset 51
- a11824050314
- parent 48
- 7e1abd8cb4e8
- child 52
- 48def27d8ddd
equal
deleted
inserted
replaced
| 50:739e353c4e97 | 51:a11824050314 |
|---|---|
| 1 ---- | 1 ---- |
| 2 Constants: | 2 Constants: |
| 3 | 3 |
| 4 * `LEAVE` - When returned will cause event callback to be cancelled | 4 * `LEAVE` - When returned will cause event callback to be cancelled |
| 5 * `EV_READ` | 5 * `EV_READ` |
| 6 * Marks read readiness/event capture. | |
| 7 * Read readiness can also mean that an 'accept' operation will succeed, or | |
| 8 a disconnection on the other end is detected (read will return nothing). | |
| 6 * `EV_WRITE` | 9 * `EV_WRITE` |
| 10 * Marks write readiness/event capture. | |
| 11 * Can also mark the successful completion of a non-blocking connect | |
| 12 if `SO_ERROR`@`SOL_SOCKET` is zero. | |
| 13 * `EV_SIGNAL` | |
| 14 * Marks signal received/event capture | |
| 7 * `EV_TIMEOUT` | 15 * `EV_TIMEOUT` |
| 16 * Timeout occurred while waiting for an event | |
| 17 * `EV_PERSIST` | |
| 18 * Marks an event as persistent and not one-shot | |
| 19 * `EV_*` | |
| 20 * Can be OR'd together to capture multiple events that make sense. | |
| 21 (Should not OR `EV_READ`/`EV_WRITE` with `EV_SIGNAL`) | |
| 22 * Can be received OR'd together. | |
| 23 For example: `EV_READ` | `EV_TIMEOUT` means that a timeout | |
| 24 occurred while waiting for a read event. | |
| 8 * `EVBUFFER_READ` | 25 * `EVBUFFER_READ` |
| 9 * `EVBUFFER_WRITE` | 26 * `EVBUFFER_WRITE` |
| 10 * `EVBUFFER_EOF` | 27 * `EVBUFFER_EOF` |
| 11 * `EVBUFFER_ERROR` | 28 * `EVBUFFER_ERROR` |
| 12 * `EVBUFFER_TIMEOUT` | 29 * `EVBUFFER_TIMEOUT` |
