<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body>
<p>This page has been created from a template that uses "zones." To proceed:</p>
<ol>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.
<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.</p></ac:rich-text-body></ac:macro></li>
</ol>
</ac:rich-text-body></ac:macro>
<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Daemon Component Proposal

Table of Contents

1. Overview

Zend_Daemon is a component to create Nix* system daemon.

2. References

• Nix* Daemon

3. Component Requirements, Constraints, and Acceptance Criteria

Basic requirements:

• This component will help forking main process to background
• This component will handle pid/pid file to ensure that only one daemon is running
• This component will chroot jail
• This component will allow running the daemon as non priviliged user
• This component will help building daemon socket based server (chat server, xml sockets,...)

4. Dependencies on Other Framework Components

• Zend_Exception
• Zend_Logger
• pcntl extension
• posix extension
• sockets extension

5. Theory of Operation

The component is an abstract class. You must extends it and override the method "main"

6. Milestones / Tasks

• Milestone 1: design notes will be published here
• Milestone 2: Working prototype [DONE]
• Milestone 3: Submit for review
• Milestone 4: Resolving the different issues and modification proposals by the community
• Milestone 5: Unit tests exist, work, and are checked into SVN.
• Milestone 6: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

• Milestone #: [DONE] Unit tests ...

7. Class Index

• Zend_Daemon_Exception
• Zend_Daemon_Abstract
• Zend_Daemon_Socket

8. Use Cases

9. Class Skeletons