[Design] Re: Design Digest, Vol 28, Issue 14
vajda at osafoundation.org
Thu Feb 16 13:20:51 PST 2006
> Issues with using headless
> - How does headless interact with a full-UI Chandler running against the
> same repository?
> - What's the footprint (CPU and memory) of headless? I like my
> background processes small.
The Chandler repository (and the underlying Berkeley DB) fully support
multiple processes running against the same repository.
It would be quite simple to write a simple daemon watching reminder items in a
Chandler repository, even while it is being actively used by Chandler.
Using headless for this may be overkill...
More information about the Design