Comments on: Web analytics API http://noteplog.com/web-analytics-api/ Just another geek who once wanted to blog... Thu, 12 Jun 2008 04:10:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Daan http://noteplog.com/web-analytics-api/comment-page-1/#comment-96 Daan Tue, 13 May 2008 09:01:27 +0000 http://noteplog.com/web-analytics-api/#comment-96 StatsPlugger (Www.statsplugger.com) is an analytics solution that works trough XML. StatsPlugger (Www.statsplugger.com) is an analytics solution that works trough XML.

]]> By: Dan Grossman http://noteplog.com/web-analytics-api/comment-page-1/#comment-2 Dan Grossman Mon, 02 Jul 2007 22:40:06 +0000 http://noteplog.com/web-analytics-api/#comment-2 I'm the author of W3Counter and its API. Most of the work of providing the API is done through PHP5's reflection classes. They provide the ability to inspect the classes that provide W3Counter's data internally, and easily generate the API reference and documentation from the method names, parameter lists, and phpdoc contained in the class files. As the classes are updated, the documentation updates itself automatically through reflection. Reflection also does most of the work for transforming an API call into an actual class method call. A search through the class for a matching method name with the right privacy level is all that's needed. Then, the remaining $_GET variables can be thrown into an array passed as parameters to call_user_func_array() to make the actual call. Returning the result is relatively automated as well. My internal classes return a custom wcDataSet class which encapsulates the data and several attributes, such as a total result count for paging. One method transforms a data set into an XML block. Thus, again, the API updates itself whenever a method is added to the class without any additional work. I’m the author of W3Counter and its API. Most of the work of providing the API is done through PHP5′s reflection classes. They provide the ability to inspect the classes that provide W3Counter’s data internally, and easily generate the API reference and documentation from the method names, parameter lists, and phpdoc contained in the class files. As the classes are updated, the documentation updates itself automatically through reflection.

Reflection also does most of the work for transforming an API call into an actual class method call. A search through the class for a matching method name with the right privacy level is all that’s needed. Then, the remaining $_GET variables can be thrown into an array passed as parameters to call_user_func_array() to make the actual call.

Returning the result is relatively automated as well. My internal classes return a custom wcDataSet class which encapsulates the data and several attributes, such as a total result count for paging. One method transforms a data set into an XML block.

Thus, again, the API updates itself whenever a method is added to the class without any additional work.

]]>