-<li>The function <tt>silc_schedule</tt> on Symbian will return immediately,
-instead of blocking the calling thread/process as on other platforms. On
-symbian the function is equivalent to <tt>silc_schedule_one</tt>, and that
-function should be used instead. The design of SilcSchedule on Symbian
-enables efficient data I/O even when <tt>silc_schedule_one</tt> is called
-from a timer task. The data I/O is scheduled separately by the Symbian
-Active Scheduler and the SilcSchedule will merely schedule timeouts.
+<li>The function <tt>silc_schedule</tt> on Symbian will allocate new Active
+Scheduler Waiter and will block the calling thread. The caller should
+allocate Active Scheduler before calling <tt>silc_schedule</tt>.
+
+<li>When adding timeout tasks to SILC Scheduler the SILC Scheduler is woken
+up after the timeout task has been added. This allows adding of the
+timeout tasks from Symbian active objects outside the SILC Scheduler loop.
+On other platforms this wakeup operation is not performed.
+
+<li>Adding fd task to SILC Scheduler will not schedule the fd for any
+operation. Instead, programmer should use SILC Socket Stream API and SILC
+Fd Stream API on Symbian when dealing with file descriptors and sockets.
+These APIs provide asynchronous notification when data is available and can
+be written.
+
+<li>The function <tt>silc_thread_create</tt> on Symbian will install Active
+Scheduler and allocate Cleanup Stack for the new thread. The created
+thread always shares heap with the parent thread.
projects / runtime.git / blobdiff