+ Example:
+ silc_schedule_task_add_event(schedule, "connected",
+ SILC_PARAM_UI32_INT,
+ SILC_PARAM_BUFFER,
+ SILC_PARAM_END);
+ silc_schedule_event_connect(schedule, "connected", connected_cb, ctx);
+ silc_schedule_event_signal(schedule, "connected", integer, buf,
+ SILC_PARAM_END);
+ SILC_TASK_CALLBACK(connected_cb)
+ {
+ FooCtx ctx = context;
+ va_list args;
+ SilcUInt32 integer;
+ SilcBuffer buf;
+
+ va_start(args, context);
+ integer = va_arg(args, SilcUInt32);
+ buf = va_arg(args, SilcBuffer);
+ va_end(args);
+ ...
+ }
+
+ Problems: Events would be SilcSchedule specific, and would not work on
+ multi-thread/multi-scheduler system. The events should be copyable
+ between schedulers. Another problem is the signal delivery. Do we
+ deliver them synchronously possibly from any thread to any other thread
+ or do we deliver them through the target schedulers. If we use the
+ schedulers then signalling would be asynchronous (data must be
+ duplicated and later freed) which is not very nice.
+
+ o If the event signals are added, the SILC_PARAM_* stuff needs to be
+ moved from silcbuffmt.h to silctypes.h or something similar.
+
+ o In case the SILC Events are done we shall create a new concept of
+ parent and child SilcSchedule's. When new SilcSchedule is created a
+ parent can be associated to it. This association could be done either
+ directly by the parent or by any other children. This way the signals
+ would in effect be global and would reach all children schedulers.
+
+ This relationship would be associative only. The schedulers are still
+ independent and run independently from each other. All schedulers
+ would be linked and could be accessed from any of the schedulers.
+ It should be possible to retrieve the parent and enumate all children
+ from any of the schedulers.
+
+ SilcSchedule silc_schedule_init(int max_tasks, void *app_context,
+ SilcSchedule parent);
+ SilcSchedule silc_schedule_get_parent(SilcSchedule schedule);
+
+ o Additional scheduler changes: optimize silc_schedule_wakeup. Wakeup
+ only if the scheduler is actually waiting something. If it is
+ delivering tasks wakeup is not needed.
+
+ o Structured log messages to Log API. Allows machine readable log
+ messages. Would allow sending of any kind of data in a log message.
+
+ o Base64 to an own API (***DONE)
+
+ o Timer API (***DONE)