<?xml version="1.0" encoding="iso-8859-1"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>
    <channel rdf:about="http://pear.php.net">
    <link>http://pear.php.net/</link>
    <dc:creator>pear-webmaster@lists.php.net</dc:creator>
    <dc:publisher>pear-webmaster@lists.php.net</dc:publisher>
    <dc:language>en-us</dc:language><items>
<rdf:Seq><rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=692"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=691"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=687"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=683"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=682"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=681"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=670"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=669"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=662"/>
<rdf:li rdf:resource="http://pear.php.net/pepr/pepr-proposal-show.php?id=660"/>
</rdf:Seq>
</items>

<title>PEPr: Latest proposals with status Proposed</title>
<description>The latest PEPr proposals with status Proposed</description>
</channel>

<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=692">
 <title>PEPr Proposal [692]: Caching::phpfastcache</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=692</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Caching::phpfastcache&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/khoaofgod&quot;&gt;Khoa Bui&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Your PHP is sending 10,000 queries extractly the same to Database. Let phpFastCache reduce it to 1 query and serve your 10,000 visitors.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;One Caching Class use for ALL cache: Files, APC, WinCache, MemCache and MemCached, XCache, PDO.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;You will never have to rewrite your code again when you change your servers&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;phpFastCache dropped the database load to almost nothing, yielding faster page load times for users, better resource utilization. It is simple yet powerful&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;More information and EXAMPLES at &lt;a href=&quot;http://www.phpfastcache.com&quot; onclick=&quot;window.open(this.href, '_blank'); return false;&quot;&gt;http://www.phpfastcache.com&lt;/a&gt;&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2013-05-13T18:45:58-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=691">
 <title>PEPr Proposal [691]: Security::phprbac</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=691</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Security::phprbac&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/abiusx&quot;&gt;Abbas Naderi&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;PHP RBAC is a standard NIST level 2 hierarchical role based access control implementation with extended features for PHP.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;From website:&lt;br /&gt;&lt;br /&gt;
PHP-RBAC is the de-facto authorization library for PHP. It provides developers with NIST Level 2 Standard Role Based Access Control and more, in the fastest implementation yet.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2013-03-01T02:43:11-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=687">
 <title>PEPr Proposal [687]: Database::DB_DataObject_FormBuilder_Frontend</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=687</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Database::DB_DataObject_FormBuilder_Frontend&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/madsliejensen&quot;&gt;Mads Lie Jensen&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Package to build frontends for database editing. The most basic use requires very little code, most is done in a config-file written in xml.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;It displays list of tables that can be edited, lists the contents of the tables and forms for editing/adding/deleting records from these tables.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Database access is done using DB_DataObjects, forms for editing is made using DB_DataObject_FormBuilder and the lists of tables or table-contents with Structures_DataGrid. This makes the behavior and output very flexible. But if not flexible enough, the package can be easily expanded using plugins and different forms of callback-methods.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Code can be found on &lt;a href=&quot;https://github.com/gartner/DB_DataObject_FormBuilder_Frontend&quot; onclick=&quot;window.open(this.href, '_blank'); return false;&quot;&gt;Github&lt;/a&gt;&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2012-12-20T06:54:13-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=683">
 <title>PEPr Proposal [683]: Date and Time::Date_Holidays_Turkey</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=683</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Date and Time::Date_Holidays_Turkey&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/alastyr&quot;&gt;Serkan Cetintopcu&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Date_Holidays helps you calculate the dates and titles of holidays and other special celebrations. This is the driver for calculating holidays in Turkey.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2012-11-23T15:18:10-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=682">
 <title>PEPr Proposal [682]: Web Services::Services_Douban</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=682</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Web Services::Services_Douban&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/doubanxia&quot;&gt;zhou yang&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;douban.com is a chinese UGC website, most users are chinese.&lt;br /&gt;&lt;br /&gt;
This package is PHP API for Douban, just like Services_Facebook.&lt;br /&gt;&lt;br /&gt;
Douban API offical site is developers.douban.com&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2012-10-23T07:17:23-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=681">
 <title>PEPr Proposal [681]: PHP::opensrf-php</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=681</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        PHP::opensrf-php&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/pranjal710&quot;&gt;Pranjal Prabhash&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Package opensrf-php is a PHP bindings for the OpenSRF library, which allows you to make requests and receive responses from OpenSRF services, such as those that comprise the Evegreen Integrated Library System (ILS) (&lt;a href=&quot;http://open-ils.org/&quot; onclick=&quot;window.open(this.href, '_blank'); return false;&quot;&gt;http://open-ils.org/&lt;/a&gt;).&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Examples of how to use the bindings to contact typical services for Evergreen are under the examples/ directory.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Setting up an OpenSRF session will retrieve the fm_IDL.xml file from the targeted server, which provides that server's Interface Description Language. This essentially means class definitions that allow certain data structures to be interpreted as objects in the Object-oriented sense.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2012-10-22T03:32:09-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=670">
 <title>PEPr Proposal [670]: Images::EllipseArc</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=670</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Images::EllipseArc&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/aekwebelam&quot;&gt;Austin Ekwebelam&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;A PHP class to draw arcs, chords, segments, crescents, circles and ellipses.  It supports thicknesses, rotations and alpha-colours.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2011-12-10T11:54:03-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=669">
 <title>PEPr Proposal [669]: Encode::Encode_Base58_GMP</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=669</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Encode::Encode_Base58_GMP&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/jwang&quot;&gt;John Wang&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Base58-GMP-PHP&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;High speed Base58 encoding using GMP with BigInt support&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Base58 is a compact, safe, and readable encoding that uses&lt;br /&gt;&lt;br /&gt;
alpha-numeric characters only (unlike Base64) and limits&lt;br /&gt;&lt;br /&gt;
the alphabet to easily readable characters, avoiding&lt;br /&gt;&lt;br /&gt;
[0OIl] (unlike Base62).&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Base58 is used by Flickr and others for URL shortening.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;This implementation uses the GNU Multiple Precision&lt;br /&gt;&lt;br /&gt;
Arithmetic Library (GMP) (&lt;a href=&quot;http://gmplib.org/&quot; onclick=&quot;window.open(this.href, '_blank'); return false;&quot;&gt;http://gmplib.org/&lt;/a&gt;) for high&lt;br /&gt;&lt;br /&gt;
speed encoding and decoding.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;A md5_base58 function is also provided for digest&lt;br /&gt;&lt;br /&gt;
generation&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2011-11-14T02:31:31-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=662">
 <title>PEPr Proposal [662]: Science::Astronomy</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=662</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Science::Astronomy&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/eru&quot;&gt;Alexander Wirtz&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Hi all,&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;I'd like to start a package containing often looked after functions for calculating moon phases, moonrise, moonset, azimuths, local sidereal time, etc., which are used in astronomical context.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Currently I've started implementing some of these functions in my other package Services_Weather, but it has grown to a point, where breaking them off makes a lot of sense.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;I just wanted to get a feeling, if this should be implemented yes or no, otherwise I continue implementing the bare necessities in Services_Weather.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Best,&lt;br /&gt;&lt;br /&gt;
Alexander&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2011-08-01T17:53:11-05:00</dc:date>
</item>
<item rdf:about="http://pear.php.net/pepr/pepr-proposal-show.php?id=660">
 <title>PEPr Proposal [660]: Version Control::VersionControl_Hg</title>
 <link>http://pear.php.net/pepr/pepr-proposal-show.php?id=660</link>
 <content:encoded>&lt;br /&gt;
Proposed package:        Version Control::VersionControl_Hg&lt;br /&gt;&lt;br /&gt;
Proposer:                &lt;a href=&quot;/user/mgatto&quot;&gt;Michael Gatto&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;VersionControl_Hg is a PEAR PHP wrapper for the Mercurial version control system. The API interface is designed to be fluid with chainable methods:&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;include 'VersionControl/Hg.php';&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;$hg = new VersionControl_Hg('/path/to/repository');&lt;br /&gt;&lt;br /&gt;
$unformatted_text_log = $hg-&amp;gt;log()-&amp;gt;after('Dec 27, 2010')-&amp;gt;excluding('**.xml')-&amp;gt;format('raw')-&amp;gt;run();&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;All mercurial commands are represented by a base method in this package:&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;hg log = $hg-&amp;gt;log()-&amp;gt;run();&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;However, there is not an exact 1-to-1 corresponence between Mercurial option names and chained helper methods. Instead, I have chosen to use full, semantic method names to make it clear how the option should modify the command. I have used Mercurial long-option names wherever they make sense, but modified them to better fit into the fluid interface.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;The initial use case is to make a useful interface to Mercurial for Phing and other deployment &amp;amp; build systems. Eventually, I plan to support all Mercurial commands.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;A Mercurial installation is required. Either the stock CLI client or TortoiseHg, which includes the CLI client. VersionControl_Hg is smart enough to search the  Path to find a viable Mercurial executable. Platform independence is a primary design goal.&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;Code, build script, and documentation is available at: &lt;a href=&quot;https://bitbucket.org/mgatto/versioncontrol_hg/overview&quot; onclick=&quot;window.open(this.href, '_blank'); return false;&quot;&gt;https://bitbucket.org/mgatto/versioncontrol_hg/overview&lt;/a&gt;&lt;/p&gt;&lt;br /&gt;
&lt;br /&gt;

 </content:encoded>
 <dc:date>2011-06-20T19:19:25-05:00</dc:date>
</item>

</rdf:RDF>