Contents

#Todo

###Known issues & Bugs

  0. A `every` event used in a controller's action will time correctly on the first action, but subsequent actions will be off by at most 3 ticks.
  This is because we do not have any way (currently) to reset the timing queue in the controller as it reisters for all timing events at init. See
  "Does not call intervals of other actions; and still works when switching back actions" in `spec/kern/controller_spec.rb` 
  1. `vm_cache_write_sync_pending` in the `vm` service relies on page_ids, but this would cause a collision on two pages named the same thing. This
   needs to integrate the namespace.
  2. The pager synchronization daemon and functions associated with marking paging as needing synchronization will attempt to sync at one time and not
  store the data if there is a crash or exit before synchronization completes. Furethermore, too many unsynced pages will wreck havok as they wil be
  dispatched at the same time via the synchronization daemon.
  3. A `watch` request on a page does technically asynchronously dispatch a disk read request at the same time the pager's request goes through. If a pager was to write
     a page before this disk read, directly via `vm_cache_write`, then the cached page would not be loaded in time.

###Ideas for improvement
  0. The `Raise` function should not actually signal the controller, it could just inline that
  1. The controller's `ctable` could be flattened.

Version data entries

22 entries across 22 versions & 1 rubygems

Version	Path
flok-0.0.105	docs/todo.md
flok-0.0.103	docs/todo.md
flok-0.0.102	docs/todo.md
flok-0.0.101	docs/todo.md
flok-0.0.100	docs/todo.md
flok-0.0.99	docs/todo.md
flok-0.0.98	docs/todo.md
flok-0.0.97	docs/todo.md
flok-0.0.96	docs/todo.md
flok-0.0.95	docs/todo.md
flok-0.0.94	docs/todo.md
flok-0.0.93	docs/todo.md
flok-0.0.92	docs/todo.md
flok-0.0.91	docs/todo.md
flok-0.0.90	docs/todo.md
flok-0.0.89	docs/todo.md
flok-0.0.88	docs/todo.md
flok-0.0.87	docs/todo.md
flok-0.0.86	docs/todo.md
flok-0.0.85	docs/todo.md