<?xml version="1.0" encoding="iso-8859-15" ?>
<rss version="2.0">
<channel>
	<title>reacties op Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update</link>
	<description>
		<![CDATA[
		
		]]>
</description>
	<image>
		<title>reacties op Important PHP Mollom update</title>
		<url>http://blog.verkoyen.eu/modules/core/layout/images/rss2.gif</url>
		<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update</link>
	</image>
	<lastBuildDate>Sat, 11 Feb 2012 18:47:19 +0100</lastBuildDate>
	<pubDate>Sat, 11 Feb 2012 18:47:19 +0100</pubDate>
	<generator><![CDATA[Fork CMS]]></generator>
	<language>nl</language>
<item>
	<title>re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6642</link>
	<description>
		<![CDATA[
			Hi Tijs,

I&#039;ve been looking into the SilverStripe Mollom module, which makes use of your class, and there are a few bugs with it - in particular, it gets into an infinite loop if the Mollom servers are down.

To fix this, I can fork our copy of the Mollom class, however, it would be nicer if we could feed our changes back into a future release of PHP Mollom.

Do you have a place where I could submit patches?  Perhaps it would be appropriate to set up a Google Code site for PHP Mollom?
		]]>
	</description>
	<pubDate>Fri, 07 Aug 2009 04:46:57 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6642</guid>
	</item>
<item>
	<title>re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6015</link>
	<description>
		<![CDATA[
			@Michiel: nee er is geen PHP4-versie. Aangezien PHP gestopt is met de support voor PHP zou ik je ook aanraden om te migreren naar PHP5. (http://us.php.net/manual/en/faq.migration5.php)
		]]>
	</description>
	<pubDate>Mon, 27 Jul 2009 22:49:40 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6015</guid>
	</item>
<item>
	<title>re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6005</link>
	<description>
		<![CDATA[
			Is er ook een PHP4 versie van deze code?
		]]>
	</description>
	<pubDate>Mon, 27 Jul 2009 16:29:38 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-6005</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-690</link>
	<description>
		<![CDATA[
			thanks..
		]]>
	</description>
	<pubDate>Sat, 16 Aug 2008 22:19:18 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-690</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-689</link>
	<description>
		<![CDATA[
			found your site on del.icio.us today and really liked it.. i bookmarked it and will be back to check it out some more later ..
		]]>
	</description>
	<pubDate>Tue, 05 Aug 2008 20:49:15 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-689</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-688</link>
	<description>
		<![CDATA[
			@Martin: All methods throw errors when something wrong you can catch them using the try catch-structure.

The remark about the IP address is a nce one, I will add it in the next version. The things you want to do are also possible with the static methods so I don&#039;t think I&#039;m going to change it into a non-static version.
		]]>
	</description>
	<pubDate>Tue, 15 Jul 2008 11:25:20 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-688</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-687</link>
	<description>
		<![CDATA[
			Sorry, I should have been more specific about what appears to be a slip.  The line looks to me as if it ought to read $servers = (array) $servers; otherwise the code is setting a value for $server (without an s) which is then overwritten by the foreach loop.

Wholly static classes are inflexible and not very efficient.  Ordinary objects will run faster than a set of static calls.  But the important point is flexibility.  For example, I want to embed the class in a substantial system that is most effectively done by subclassing your class.  That can&#039;t be done with set of static methods.  One thing I&#039;d like to do in the subclass is to set the public and private keys in the constructor, using information held in a standard configuration.  That way, users of the subclass do not need to know where to find the keys, or need to do anything about them.  The system also has a mechanism for finding the IP address of the requestor, and I&#039;d prefer to be able to override the given method (which is perfectly ok) with the system method for the sake of consistency.  Also, I might be inclined to override an error raising method (if there were one).

Having done all that, it might be helpful to further subclass the subclass for specific applications so that use within an application is as simple as possible.  And other people might have other ideas!

In this case, I&#039;d not be too worried about creating multiple objects, since the data can still be class data (i.e. static).  But it would still be possible to provide one or more static methods by turning the class into a singleton, while also providing for the flexibility and efficiency mentioned earlier.

I&#039;ve actually adapted the class to avoid being static methods, and will gladly send it to you if you&#039;d like.  I&#039;d much rather you carry on with the maintenance than me have to do it :)
		]]>
	</description>
	<pubDate>Tue, 15 Jul 2008 11:17:15 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-687</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-686</link>
	<description>
		<![CDATA[
			@Martin again: Maybe I should say why I choose to to use a static class in favor of instances.
 WIth the static way you can require Mollom and add Mollom::set...Key in your init-object (or configfile).

Once that is done you can use Mollom everywhere in your application without passing instances or creating instance again.

I think this way Mollom is more flexible. But explain to me why I should use instances instead off a static class?
		]]>
	</description>
	<pubDate>Tue, 15 Jul 2008 10:59:46 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-686</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-685</link>
	<description>
		<![CDATA[
			@Martin: Why should it be an &quot;proper&quot; object? Why should I create multple instances of Mollom? Now you don&#039;t have to create an instance.
Btw, I can&#039;t see whats wrong with tha line. I redefine it, so I know for sure it is an array. Otherwise the foreach will trigger notices.
		]]>
	</description>
	<pubDate>Tue, 15 Jul 2008 10:35:44 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-685</guid>
	</item>
<item>
	<title>Re: Important PHP Mollom update</title>
	<link>http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-684</link>
	<description>
		<![CDATA[
			I might be mistaken, but should the method setServerList have the first executable line as &quot;$servers = ...&quot;?  To coerce the parameter into being an array?

	public static function setServerList($servers)
	{
		// redefine
		$server = (array) $servers;

		// loop servers
		foreach ($servers as $server) self::$serverList[] = $server;
	}

The class is nice, but would be nicer if it were a proper object rather than a bunch of static methods.
		]]>
	</description>
	<pubDate>Tue, 15 Jul 2008 10:27:28 +0200</pubDate>
	<guid isPermaLink="true">http://blog.verkoyen.eu/blog/p/detail/important-php-mollom-update/#reactie-684</guid>
	</item>
</channel>
</rss>

