Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
New Proposal Template
This page has been created from a template that uses "zones." To proceed:
  1. Edit the page
  2. Replace sample content within each zone-data tag with your own content
  3. Remove this notice
  4. Save the page
  5. When you are ready for community review, move this page to the Ready for Review section on the edit page.
    No placeholders allowed!
    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.

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

Zend Framework: Zend_Daemon Component Proposal

Proposed Component Name Zend_Daemon
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Daemon
Proposers Sebastien Cramatte
Zend Liaison TBD
Revision 1.0 - 4 July 2009: Initial Draft. (wiki revision: 9)

Table of Contents

1. Overview

Zend_Dameon is a component to ceate Nix* system daemon.

2. References

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 and submit for review
  • Milestone 3: Resolving the different issues and modification proposals by the community
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: 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

UC-01

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.