9 Commits

Author	SHA1	Message	Date
Ondrej Zajicek	b933281ed5	Fixes nasty bug in event processing. ... WALK_LIST_DELSAFE (in ev_run_list) is not safe with regard to deletion of next node. When some events are rescheduled during event execution, it may lead to deletion of next node and some events are skipped. Such skipped nodes remain in temporary list on stack and the last of them contains 'next' pointer to stack area. When this event is later scheduled, it damages stack area trying to remove it from the list, which leads to random crashes with funny backtraces :-) .	2008-12-18 23:26:08 +01:00
Martin Mares	58f7d004fd	Fixes to the progdoc.	2000-06-07 13:25:53 +00:00
Martin Mares	525fa2c1f0	Documented sockets, events and timers.	2000-06-05 12:19:12 +00:00
Martin Mares	8f6accb5bb	Event handlers no longer return re-queue flag. Instead of using it, just ... call ev_schedule() on the same handler which should work perfectly now.	2000-04-27 22:28:49 +00:00
Martin Mares	ebc793a5f5	No more problems when events get scheduled during event processing.	2000-01-16 17:39:16 +00:00
Martin Mares	84a7d7f77c	ev_run() now returns whether the event has been requeued or not. ... ev_run_list() now returns number of events which remain in the list.	1999-11-17 12:01:11 +00:00
Martin Mares	0d70292d88	Events now return a value. If it's non-zero, the event is re-queued ... for processing in next event cycle. This can be used to prevent background actions (hint: user commands) from hogging the CPU for too long time.	1999-10-29 12:08:49 +00:00
Martin Mares	67bd949a52	Real implementation of protocol state machines. Delayed startup/shutdown ... should work now. Initial feeding of protocols by interfaces/routes is done from the event queue to prevent unwanted recursion.	1999-02-11 22:59:06 +00:00
Martin Mares	3b15402fd4	Grrr, forgot to commit the event routines themselves :|	1999-02-11 22:18:36 +00:00