The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Jan 08, 2008
PHP, one of the cornerstones of LAMP stack, is used by major websites such as Wikipedia. Designed as a server-side language, it normally has to be paired with JavaScript or Flash/ActionScript to build rich Internet applications.
Silverlight, like the rest of the Common Language Runtime, is in theory language-agnostic. In the past it has posed some problems for dynamic languages, which lead to the development of the Dynamic Language Runtime or DLR. The DLR provides a unified object model for dynamic languages and the ability to host just-in-time compilers needed for so-called scripting languages.
Tomas Petricek is leveraging Silverlight and the DLR to allow PHP developers to use their current skill set and libraries on the client. The core of this setup is two files, PhpNetCore.dll and PhpNetClassLibrary.dll. The first is a PHP compiler for .NET, the latter a collection of common PHP functions. When referenced from an XAML file, they allow PHPX files to be loaded and run from within Silverlight.
Because everything is done client-side, there should be no reason why Linux-based web servers that PHP developers prefer cannot be used to host the Silverlight applications.
You can learn more about Silverlight/PHP integration on Tomas Petricek's blog.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A practical guide to choosing the right agile tools
Mobile and the New Two-Tiered Web Architecture
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Agile Maturity Model Applied to Building and Releasing Software
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
No comments
Watch Thread Reply