Port 25: The Open Source Community at Microsoft : PHP, .NET Development

Windows Cache Extension 1.0 for PHP Released

Peter Galli — Fri, 20 Nov 2009 00:40:00 GMT

The Microsoft Internet Information Services (IIS) team announced today the release of Windows Cache Extension 1.0 for PHP, a PHP accelerator that is used to increase the speed of PHP applications running on Windows and Windows Server. This is a production-ready release that is provided under an open source BSD license, with the source code hosted and maintained here, and the documentation hosted on php.net.

You can find more details on this release on IIS team Product Unit Manager Mai-lan Tomsen Bukovec's blog.

WinCache extension is a significant open source contribution from Microsoft to the PHP on Windows community. The extension code is hosted and maintained on PHP Extensions Community Library (PECL) and is available for everyone to view, branch, compile, and contribute to.

The IIS team also invites the PHP development community to join it in development of this caching extension for PHP on Windows. There have already been some contributions from the community whileWinCache was in the pre-release mode, and IIS team is looking forward to having others join this new PHP on Windows caching project.

Also, in time for this release, an independent PHP company - Ibuildings - has conducted a benchmark test with the WinCache RTW bits and published the results.

The release of this production-ready PHP accelerator for Windows is an important step towards making the Windows operating system an even better platform for hosting PHP applications.

WinCache extension significantly improves performance of PHP applications and lowers CPU load on the server. This, together with the fact that no application code changes are necessary to take advantage of the caching, makes WinCache a must have extension when running PHP on Windows.

More information about the WinCache extension for PHP can be found as follows:

The PECL documentation on WinCache
The PHP on Windows feature team blogs (Kanwal, Ruslan, and Don)
The WinCache community forum
The IIS.NET documentation on WinCache
The WinCache on PECL source code, licensed under BSD
How to file bugs on WinCache in PECL

The Hidden Technology Decision-Maker

Mark Stone — Wed, 25 Mar 2009 15:00:00 GMT

On Monday Microsoft and SD Forum held the 3rd annual Open Source ISV Forum. In a day of interesting talks, I was particularly struck by Larry Augustin's talk. As an emphasizing example of the growth of open source projects partnered with a commercial endeavor, Larry mentioned DotNetNuke.

DotNetNuke is, of course, freely available for download and licensed under an open source license. But there is also a professional edition and a range of complimentary commercial services for those who want service, support, or customizations. The business model is classic open source: the free download seeds the market with potential customers, and as some of those run up against the limits of what they are willing to do on their own, they make inquiries about the professional edition. Thus open source creates an inbound channel of qualified sales leads, without the overhead and expense of a sales force working in the field.

This is a great business model, but it's important to think about the actual decision-makers in this adoption process. What's distinctive about DotNetNuke is that it's one of the few mature, open source Content Management Systems (CMSs) that is not written in PHP. It is, as the name implies, ASP.NET based. And this reminds me of a prdocut management position I was in some years ago when (a) the only mature CMS choices were PHP-based, and (b) PHP on Windows was not yet a viable alternative.

The company in question was in a typical position: they were not a technology company, but needed a strong web presence for their business and to connect to the online community of their customers. They had a home-grown CMS solution that wasn't scaling, wasn't secure, and wasn't stable. My product management team put together a good comparison chart of various CMS choices, many of them open source. I sat down with the web development manager to review the choices.

"Some of these are good systems," he said, "but I have a team of .NET developers, and these are all PHP-based. I don't have head count to go out and hire a PHP dev for this project."

Note the decision-making process at work here:

From an agreed list of candidate software, an engineering team will download something to "test drive";
One developer will do some testing and make a recommendation;
From a short list of recommended software a more thorough test will be done with a prototype or pilot project;
Finally a choice will be made, and money will be spent.

The person with the first vote in the process is not a CIO or any other traditional "IT Decision Maker". It's one dev, talking to his manager. If your software gets vetoed at that level, or -- worse -- never even gets a try-out, then your product isn't in the decision-making process.

A lot has changed in recent years. PHP is now much better supported on Windows, and .NET projects like DotNetNuke are available and much more mature. This is as it should be. For open source to spread to its full potential, it has to be available in the technology adoption decision-making process. And that availability starts with being available to the hidden technology decision-maker: that lone developer who will look at software written in a framework they understand for a platform they work with.

Better Tools for Web Development

Mark Stone — Wed, 18 Mar 2009 15:10:00 GMT

Several years ago I was helping a musician friend of mine set up a web site to use as a promotional site for his live performances. I opted for a simple, PHP-based Content Management System (CMS) that wouldn’t require any special knowledge for him to post new information, and would be – famous last words – easy for me to set up and maintain.

Not having done professional web development for some time, I quickly found myself on the phone to one of my PHP guru friends. After editing three configuration files (two for the web server, one for PHP itself), and adjusting to make sure we had the right version of PHP running with the right version of MySQL, we finally got everything working, and the CMS properly installed and configured.

This small example has several instructive lessons:

Getting software components working together properly is hard. The open source community takes real pride in tackling this challenge, having delivered tools like make, dpkg, and apt. Even so, simple cases can fail and mire you in complexity.
None of this is where web developers want to spend their time. The creative, innovative work is all done once you have the right components in place.
Absent perfect tools (which we’ll probably never have), you want to have the collective knowledge of your developer community working for you. Without my friend on the phone, I’d have had a much bigger problem on my hands.

So there’s something very liberating about seeing Microsoft offer better tools and facilitate better community collaboration so that web developers can spend more time on creative work and less on component complexity.

I’m referring specifically to the Microsoft Web Platform: Web Platform Installer 2.0 Beta (WebPI) and Windows Web Application Gallery, announced today at MIX ’09.

WebPI provides a single online destination and a single process for downloading and installing Microsoft’s freely available web products. By itself this may seem like no more than much-needed common sense, a good effort by Microsoft to help web developers get all the components they need working together more easily and more effectively.

What makes this development really interesting is the Web Application Gallery, an opportunity for web developers to participate and collaborate in a knowledge marketplace of shared components. In other words any web developer who follows certain basic guidelines can add their product to the Gallery, and be part of this ecosystem/community of shared web development activity. This is an opportunity not just to market your work, but share ideas and innovations with other web developers, and indeed let them build on your work.

Does that sound reminiscent of an open source community? It should. While there is no requirement that Gallery code be open source, the spirit behind this effort is very much one of collaboration. The Gallery is based on the idea that web developers collectively can advance their work more than each can individually.

Nor is this a playground strictly for Microsoft technologies. There are two supported web development frameworks in the Gallery: .NET and PHP. Opening up the world of PHP applications for Windows is an exciting prospect. There is at least the possibility that something like Word Press on Windows Server will be a point and click install. We aren’t there yet. WebPI installs SQL Server by default, and MySQL is still a manual install. Many web developers won’t – or shouldn’t – care about the difference, but to some it will matter.

But this is definitely a step along the right path, one step closer to making PHP an operating system-agnostic language. Because a PHP developer should care only about building great apps.

A Technical Look at ASP.NET AJAX

MichaelF — Fri, 02 Feb 2007 21:36:00 GMT

Following up on our post yesterday here is an interview Sam did with ASP.NET Technical Evangelist: Steve Marx.

Steve discusses the three components of ASP.NET AJAX and shows us a demo of the software formerly known as ATLAS running on top of PHP on Linux to demonstrate some of the front and backend extraction capabilities.

Video: A Technical Look at ASP.NET AJAX

If you are interested in looking a bit more deeply at ASP.NET AJAX, as well as the PHP support Steve released to Codeplex, here are some links he provided:

ASP.NET AJAX: http://ajax.asp.net/
Direct link to download the Microsoft AJAX Library: http://ajax.asp.net/downloads/library/default.aspx?tabid=47
PHP for Microsoft AJAX Library: http://codeplex.com/phpmsajax
Steve's Blog: http://smarx.com/