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_Uuid Component Proposal

Proposed Component Name Zend_Uuid
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Uuid
Proposers Christoph Kempen
Danny Verkade
Zend Liaison TBD
Revision 0.1 - 11 March 2010: Initial Draft. (wiki revision: 19)

Table of Contents

1. Overview

Zend_Uuid is a simple component that generates a UUID according to the RFC 4122 standard. Only support for version 1, 3, 4 and 5 UUID are built-in.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will generate UUIDs strictly complying with RFC 4122.
  • This component will use /dev/urandom on *nix platforms.
  • This component will use CAPICOM's getRandom method on Windows platforms.
  • This component will compare UUIDs in different formats (eg. canonical string, lowercase hex string, uppercase hex string, binary, URN).
  • This component will import UUIDs and transform them to a different format.

4. Dependencies on Other Framework Components

  • Zend_Exception

5. Theory of Operation

You can use Zend_Uuid to quickly generate a UUID.

6. Milestones / Tasks

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

  • Milestone 1: design notes will be published here
  • Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
  • Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
  • 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_Uuid
  • Zend_Uuid_Exception

8. Use Cases

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.