{"id":189,"date":"2011-10-05T13:44:12","date_gmt":"2011-10-05T18:44:12","guid":{"rendered":"http:\/\/blogs.wp.stage.cpanel.net\/?p=189"},"modified":"2011-10-05T13:44:12","modified_gmt":"2011-10-05T18:44:12","slug":"livephp","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/livephp\/","title":{"rendered":"LivePHP"},"content":{"rendered":"

Currently, if you want to write a Plugin for cPanel, you can write it in either LivePHP<\/a> or cPPHP<\/a>. Last year, we put some major effort into refactoring LivePHP. We added better debugging information, optimized the socket communication protocol, and added a few other tweaks. After a year of vetting by external developers, I can say with confidence: there is no longer any reason to use cPPHP when developing your application.<\/em> <\/p>\n

cPPHP is a system that requires cPanel to parse cPanel tags and then run the result through the PHP interpreter. Alternately, it can run your code through a PHP interpreter, then parse out cPanel tags, depending on file extension. This system has a few major disadvantages.<\/p>\n

Consider the following standard use case:<\/p>\n