I recently wrote a PHP script to scrape data from a .NET application. In the process of developing this script, I noticed something interesting that I thought I'd share. In this case, I was using the cURL extension, but the tip isn't necessarily specific to that. One thing my script did was submit a POST request to simulate a form submission. [...] The issue I ran into had to do with a behavior of the CURLOPT_POSTFIELDS setting that's easy to overlook.

The problem was something cURL does automatically - change the header for the content type because you're sending an array. Thankfully, with the help of a call to http_build_query to encode it correctly, the request will use the right headers.

New web development frameworks, promising rapid development and easy deployment, are sprouting out at a more rapid pace than you can keep up. In the last article, we looked at the various factors you'd have to consider when deciding on a framework. Today, we are going to look at the various frameworks available for each facet of web development.

PHP tools that made the list include CakePHP, the Zend Framework, Kohana and Symfony. Frameworks from some of the other languages include ASP.NET, Ruby on Rails, jQuery and Blueprint.

Zero doesn't currently support the COM/.NET extension in PHP. No matter though, there is a handy open source project called JACOB that bridges between Java and COM/.NET. In fact, there is an easier way to do this using a Groovy library called Scriptom. This is really just a friendly wrapper around JACOB to provide a better syntax for calling methods and accessing properties.

He also includes a quick introduction and howto on getting the functionality up and working in a Windows environment - download, add the JAR to your path, edit your php.ini and copy and paste some example code in to see it in action.

The difference between PHP and ASP is that ASP is a Microsoft product based on visual basic syntax whereas PHP has C and Java based syntax. ASP works better on Microsoft servers.

He describes the target audience for each language and talks about the environments that they work best in as well as some general statements about their speed and flexibility. Basing his judgment on the facts he noted, he suggests PHP as the best alternative of the two for being more flexible, running in more places and being a bit faster overall.

Now, at a programming level, a new initiative which could finally reconcile the great divide between PHP and .NET programming languages for the good of everyone - courtesy of WCM vendor Jadu. Development of the Phalanger PHP compiler was funded by the firm, but it is now releasing it into the open source community. It basically enables the creation of PHP applications which can run natively under the .NET Framework, allowing firms to make use of PHP apps without needing to rip out existing .NET/Visual Studio environments.

Phil Muncaster (author of the post) suggests that this technology is another reason to remove the "walled gardens" some .NET developers have put up and left in the flexibility and power that PHP has to offer their online development world (and vice versa).

He summarizes the functionality in three different methods of handling: "page/file based", "action based", and "component based". He also notes that the interesting fact is that the "page/file based" method seems to be so dominant in the PHP world, only emphasizing the fact that PHP is more of a "get it done" language than anything.

PHP, .net and Silverlight will be integrated out of the box, along with Visual Studio 2008. The project has long been in the works, but our sources have informed us of an impending announcement that PHP 6 will ship with .net.

The glue between them is a part of the phlanger project.

From the inital post:

I am wondering why there isn't any effort in the PHP community to get PHP into the DLR. If nothing, DLR is yet another platform, and for a php programmer it gives one more playground to showcase his skillset. Anyway, my question is whether there would be any community effort to get MS adopt PHP into CLR too. I am sure there is a genuine customer requirement, and enterprises have made quite a bit of investment in PHP and they would all love to be able to take it to the .NET platform.

Responses so far include the pointing out of problems, possibilities like a Zend collaboration and lots of talk on what such a project would entail.

As I mentioned previously, I'll be at MIX this year on a panel discussing ASP and PHP interoperability, along with Jesse Liberty, Bill Staples, Joe Stagner and Brian Goldfarb.

I've been told that MIX has sold out and that there is a lot of interest in our slot, so I'm sure we'll have plenty to talk about, but I'm looking for questions to break the ice and get things rolling.

If you know a little bit about the topic and would like to help out with questions of your own, send them along to Wez via email - wez@php.net.

They start with the install of Apache 2 via the package manager/installer apt-get (different packages depending on which style you prefer - mpm-prefork or mpm-worker). With that installed, the web server should be up and working. Next up is MySQL, installed in a similar way and enabled in the php.ini file as a module.

Finally, PHP is installed and support for it is added into the http.conf file for Apache. There's also a brief mention of installing ASP via a mod_perl package as well.