<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Anatoliy Belsky - PHP5</title>
    <link>http://belsky.info/</link>
    <description>That's what I'm thinking ...  </description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Turn PHP non public class/object methods available</title>
    <link>http://belsky.info/archives/28-Turn-PHP-non-public-classobject-methods-available.html</link>
            <category>C/C++</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/28-Turn-PHP-non-public-classobject-methods-available.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=28</wfw:comment>

    <slash:comments>5</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=28</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Anyone who did unit testing in PHP knows that private methods are untestable. One workaround for this could be to make no private but protected only members and to call methods using a proxy class. Another approach I&#039;d like to present here is a small extension hack. &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/28-Turn-PHP-non-public-classobject-methods-available.html#extended&quot;&gt;Continue reading &quot;Turn PHP non public class/object methods available&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 17 Sep 2009 22:46:02 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/28-guid.html</guid>
    
</item>
<item>
    <title>Making server side playlist with PHP</title>
    <link>http://belsky.info/archives/26-Making-server-side-playlist-with-PHP.html</link>
            <category>Linux</category>
            <category>PHP5</category>
            <category>Web</category>
    
    <comments>http://belsky.info/archives/26-Making-server-side-playlist-with-PHP.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=26</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=26</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Hi again,&lt;br /&gt;
&lt;br /&gt;
whole last week I was mad about hearing music. I&#039;ve heared tons of mp3&#039;s and radio stations over the internet.  After a couple of days hearing music at work and at home I was really bored with creating and syncronizing playlists/files. Based on this, I came to the idea to make an online playlist which I would must update only one time and in one place and it would be accessible from anywhere. The idea was easy brougth out with PHP. So just a light reading for you:&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/26-Making-server-side-playlist-with-PHP.html#extended&quot;&gt;Continue reading &quot;Making server side playlist with PHP&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 02 Oct 2008 19:36:35 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/26-guid.html</guid>
    
</item>
<item>
    <title>Gender PHP Extension</title>
    <link>http://belsky.info/archives/25-Gender-PHP-Extension.html</link>
            <category>C/C++</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/25-Gender-PHP-Extension.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=25</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=25</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Hi there,&lt;br /&gt;
&lt;br /&gt;
last week I wrote a PHP port for Joerg Michael&#039;s gender program. The program stands for gender recognition based on firstnames and has a base of &gt;40000 firstnames from around the world. I hope the stuff is deserved to be accepted on PECL.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/25-Gender-PHP-Extension.html#extended&quot;&gt;Continue reading &quot;Gender PHP Extension&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 24 Aug 2008 21:25:41 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/25-guid.html</guid>
    
</item>
<item>
    <title>Phurple - per se PHPurple</title>
    <link>http://belsky.info/archives/23-Phurple-per-se-PHPurple.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/23-Phurple-per-se-PHPurple.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=23</wfw:comment>

    <slash:comments>71</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=23</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Hey you all (and me too) web developers. The huge important news today is - now we can send IMs from a script running within a web server - isn&#039;t it cool? Only one restriction conditioned by libpurple itself is there - use is definitely safe within CGI environment only. The second important news, as you see from the title - the project was renamed to Phurple. Furthermore there are a couple essential changes I was made as refactoring of the code was written so far.&lt;br /&gt;
&lt;br /&gt;
Became interested? Lets look onto most important points in the changelog:&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/23-Phurple-per-se-PHPurple.html#extended&quot;&gt;Continue reading &quot;Phurple - per se PHPurple&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 08 Aug 2008 23:58:00 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/23-guid.html</guid>
    
</item>
<item>
    <title>PHPurple v0.3 alpha released</title>
    <link>http://belsky.info/archives/22-PHPurple-v0.3-alpha-released.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/22-PHPurple-v0.3-alpha-released.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=22</wfw:comment>

    <slash:comments>19</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=22</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    So, new PHPurple version was issued yesterday and is downloadable from sf.net. What&#039;s inside:&lt;br /&gt;
&lt;br /&gt;
* PurpleAccount::isConnecting() added&lt;br /&gt;
* PurpleAccount::getUserName() added&lt;br /&gt;
* PurpleAccount::getPassword() added&lt;br /&gt;
* PurpleClient::deleteAccount() added&lt;br /&gt;
* PurpleClient::findAccount() added&lt;br /&gt;
* PurpleClient::addAccount returns now a PurpleAccount instance (but was null)&lt;br /&gt;
* PurpleClient::authorizeRequest() added&lt;br /&gt;
&lt;br /&gt;
The most interesting thing there is of course the remote client authorization. &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/22-PHPurple-v0.3-alpha-released.html#extended&quot;&gt;Continue reading &quot;PHPurple v0.3 alpha released&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 01 Jul 2008 18:53:34 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/22-guid.html</guid>
    
</item>
<item>
    <title>Functions vs. inline code</title>
    <link>http://belsky.info/archives/21-Functions-vs.-inline-code.html</link>
            <category>Perl</category>
            <category>PHP5</category>
            <category>Python</category>
    
    <comments>http://belsky.info/archives/21-Functions-vs.-inline-code.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=21</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=21</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Recently I had a little discussion about our style guide with one of the co-workers. And the matter was concerning the line length. Most default is to limit the line length with 79-85 characters - because of terminals, printing etc. But an other question took my head in the middle of the conversation: limiting the line length would mean for example to encapsulate deep included blocks of the code into functions - sounds not bad, but ... &lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/21-Functions-vs.-inline-code.html#extended&quot;&gt;Continue reading &quot;Functions vs. inline code&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 22 Jun 2008 16:56:22 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/21-guid.html</guid>
    
</item>
<item>
    <title>PHPurple v0.2 alpha released</title>
    <link>http://belsky.info/archives/20-PHPurple-v0.2-alpha-released.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/20-PHPurple-v0.2-alpha-released.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=20</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=20</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Today I&#039;ve maked the second PHPurple release and changed it&#039;s status to alpha. The changes, came into it, are:&lt;br /&gt;
&lt;br /&gt;
* fixed zts compatibility&lt;br /&gt;
* implemented the loopHeartBeat method&lt;br /&gt;
* the runLoop method was changed to set the heartbeat interval&lt;br /&gt;
* fixed memory leak on empty alias&lt;br /&gt;
* purple.debug_enabled is now boolean&lt;br /&gt;
&lt;br /&gt;
The most interesting on this release is the PurpleClient::loopHeartBeat() story, which is of course implemented with g_timeout_add. Take a look at the new example script to see how it works.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/20-PHPurple-v0.2-alpha-released.html#extended&quot;&gt;Continue reading &quot;PHPurple v0.2 alpha released&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sat, 31 May 2008 07:44:20 +0200</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/20-guid.html</guid>
    
</item>
<item>
    <title>PHPurple 0.1.0 pre-alpha</title>
    <link>http://belsky.info/archives/14-PHPurple-0.1.0-pre-alpha.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/14-PHPurple-0.1.0-pre-alpha.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=14</wfw:comment>

    <slash:comments>35</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=14</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    The first pre-alpha is released and can be downloaded at &lt;a href=&quot;http://sourceforge.net/projects/phpurple/&quot;&gt;http://sourceforge.net/projects/phpurple/&lt;/a&gt;. The common documentation I&#039;ve started to make was placed to &lt;a href=&quot;http://phpurple.rubay.de/&quot;&gt;http://phpurple.rubay.de/&lt;/a&gt;. &lt;br /&gt;
&lt;br /&gt;
The main features implemented are:&lt;br /&gt;
&lt;br /&gt;
- send and recieve IMs&lt;br /&gt;
- fully implemented account dsn like string&lt;br /&gt;
- ability to make account specific settings&lt;br /&gt;
- basic work with buddy, buddy group and buddy list&lt;br /&gt;
&lt;br /&gt;
&lt;strike&gt;The license was changed to the BSD like proprietary license.&lt;/strike&gt;&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/14-PHPurple-0.1.0-pre-alpha.html#extended&quot;&gt;Continue reading &quot;PHPurple 0.1.0 pre-alpha&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 02 Mar 2008 16:14:37 +0100</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/14-guid.html</guid>
    
</item>
<item>
    <title>phpurple new oo design, </title>
    <link>http://belsky.info/archives/11-phpurple-new-oo-design,.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/11-phpurple-new-oo-design,.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=11</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=11</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    and so it will be in the future ... &lt;br /&gt;
&lt;br /&gt;
Namely, i had the excellent oo design suggestion from the Alexey on the pecl mailing list (and it is better, than I could invent), and it works fully for php 5.3 and unfortunately partly for php 5.2. So lets take a look on it ... just get the latest version ... &lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;&lt;b&gt;CODE:&lt;/b&gt;&lt;/div&gt;&lt;div&gt;user@host~# svn co https://phpurple.svn.sourceforge.net/svnroot/phpurple/trunk phpurple&lt;/div&gt; &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/11-phpurple-new-oo-design,.html#extended&quot;&gt;Continue reading &quot;phpurple new oo design, &quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sat, 12 Jan 2008 19:43:31 +0100</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/11-guid.html</guid>
    
</item>
<item>
    <title>phpurple</title>
    <link>http://belsky.info/archives/10-phpurple.html</link>
            <category>C/C++</category>
            <category>Linux</category>
            <category>PHP5</category>
            <category>PHP5 extentions</category>
    
    <comments>http://belsky.info/archives/10-phpurple.html#comments</comments>
    <wfw:comment>http://belsky.info/wfwcomment.php?cid=10</wfw:comment>

    <slash:comments>20</slash:comments>
    <wfw:commentRss>http://belsky.info/rss.php?version=2.0&amp;type=comments&amp;cid=10</wfw:commentRss>
    

    <author>nospam@example.com (Anatoliy Belsky)</author>
    <content:encoded>
    Some time ago i&#039;ve started to write the binding for the libpurple, the im lib. About 3-4 weeks ago i had a simple functional implementation, which i&#039;ve presented on php pecl and libpurple mailing lists. Subsequently i&#039;ve completely revised the whole thing to be OO and would present it again. There is the same minimal functionality implemented, but all is OO. So, lets begin. First install the php development package and get the code:&lt;br /&gt;
&lt;br /&gt;
&lt;div&gt;&lt;b&gt;CODE:&lt;/b&gt;&lt;/div&gt;&lt;div&gt;user@host~# svn co https://phpurple.svn.sourceforge.net/svnroot/phpurple/trunk phpurple&lt;/div&gt;&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://belsky.info/archives/10-phpurple.html#extended&quot;&gt;Continue reading &quot;phpurple&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 24 Dec 2007 19:39:46 +0100</pubDate>
    <guid isPermaLink="false">http://belsky.info/archives/10-guid.html</guid>
    
</item>

</channel>
</rss>