phing is pretty much ant written in PHP where phpUnderControl adds support for PHP projects to CruiseControl and uses phing or ant on the backend to parse the build.xml file and run commands.

I just set up CruiseControl and phpUnderControl and it’s been working great. It checks out my SVN, runs it through phpDocumentor, PHP_CodeSniffer, and PHPUnit whenever we do a check in. Since it’s all based off of the build.xml file you can run just about any software you want through it.

We’ve been using Phing, and the cost to set it up has been very low; it’s really easy to learn even if you don’t know ANT. I’ve had very bad experiences with CruiseControl (instability – going down randomly) – so I like the simplicity of Phing. Plus, it’s easily extensible using PHP (in case you have a custom task that they don’t support out of the box).

Consider that users might only use one specific syntax element in a posting, so you’d have to check for everything. Looking for “h1.” obviously only works if the user uses exactly that element.

It’s pretty easy with things like headers, but consider that markdown formats *this* as this and Textile will convert that to this instead. So you’d have ambiguous syntax constructs that would yield different results in each language.

I’d suggest going with a user choice. Try to find out what syntax is generally preferred by your users (or you), offer an “use x instead of y” checkbox for those who want the other choice.

Auto-detection, I don’t know, both are based on “natural” typing.
Perhaps you can ask the user to choose a format, with a pair of radio-buttons or something.

I specifically said I do not need this for canvas applications (as that is trivial to do), but on Facebook Pages! This is done with profile.setFBML and data published that way does reside on the facebook servers.

Infinite sessions keys do not exist anymore
Every feed is unique. But even if it weren’t, can I just stuff the fbml.refreshRefUrl in a cron job and it will work without session (because I can not get an infinite session)= Or maybe I first need to request the offline_access extended permission? Is there any way without using cron jobs?

Zlib provides C APIs, and is part of the PHP functional API as well.

gzip is one of the most (if not the most) popular compression scheme. PHP has supported it since version 4. If you need even better compression, consider bzip2.

This is just a wild guess, but try to add all the directives from eaccelerator.ini to php.ini. First create a < ?php phpinfo(); ?> and check where it’s located.

For example, try this:

[eAccelerator]
extension="eaccelerator.so"
eaccelerator.shm_size="32"
eaccelerator.cache_dir="/tmp"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"

Another thing you could do is set all the settings on run-time using ini_set(). I am not sure if that works though or how effective that is. 🙂 I am not familiar with eAccelerator to know for sure.

You have two options:

1) php_mssql extension : If you’d like something that has the same API mysql and mysqli has, then use the php_mssql extension. But there is a catch, the bundled ntwdblib.dll file with PHP is not working. You have to find this file from a SQL Server 2000 installation or you can find it on the Internet. This API is supposedly not very reliable but I have been using it without problem for about one year.

http://ca.php.net/mssql

2) Microsoft SQL Server 2005 PHP Driver : If you’d like something more modern but which does not have the same API and is missing some important functions (mssql_num_rows). The big plus is that it is supported by Microsoft and is likely to work with a future version.

http://msdn.microsoft.com/en-us/data/cc299381.aspx

PHP provides an extension for accessing Microsoft SQL Server databases. To use the SQL Server extension, all that is required is to activate the extension in the PHP configuration file.

Details on the MSDN page

I’d recommend looking at the DOM functions over the SimpleXML ones – it’s much more robust. Not as simple, but definitely has more features.

I develop and maintain a large PHP/MySQL application. Here is my experience with stored procedures.

Over time our application has grown very complex. And with all the logic on the php side, some operations would query the database with over 100 short queries.

MySQL is so quick that the performance was still acceptable, but not great.

We made the decision in our latest version of the software to move some of the logic to stored procedures for complex operations.

We did achieve a significant performance gain due to the fact that we did not have to send data back and forth between PHP and MySQL.

I do agree with the other posters here that PL/SQL is not a modern language and is difficult to debug.

Bottom Line: Stored Procedures are a great tool for certain situations. But I would not recommend using them unless you have a good reason. For simple applications, stored procedures are not worth the hassle.

When using stored procedures with MySQL, you will often need to use the mysqli interface in PHP and not the regular mysql interface.

The reason for this is due to the fact that the stored procedures often will return more than 1 result set. If it does, the mysql API can not handle it and will you get errors.

The mysqli interface has functions to handling these multiple result sets, functions such as mysqli_more_results and mysqli_next_result.

Keep in mind that if you return any result set at all from the stored procedure, then you need to use these APIs, as the stored procedure generates 1 result set for the actual execution, and then 1 additional one for each result set intentionally returned from the stored procedure.

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident.

Thanks