Port 25: The Open Source Community at Microsoft : Community, Interop, Java

New Bridge Broadens Java and .NET Interoperability

Peter Galli — Tue, 29 Sep 2009 15:31:00 GMT

Microsoft continues to deliver on its ongoing promise to build bridges between different technologies, and this week jointly announced with Noelios Technologies a new interoperability bridge between Java and .NET through REST.

The Microsoft Interoperability Technical Strategy team has been working with Noelios to build an extension to the Restlet Framework. As such, Noelios has released a new bridge for Java and .NET. It is shipping a new version of the Restlet open source project, a lightweight REST framework for Java.

This includes the Restlet Extension for ADO.NET Data Services, which makes it easier for Java developers to take advantage of ADO.NET Data Services, a set of recently added .NET Framework features that provides a simple way to expose a wide range of data sources, such as relational databases, XML files, and so on, through a RESTful service interface.

This announcement is yet another example of Microsoft's continued commitment to openness and interoperability, and demonstrates the ever increasing use of web standards in our technologies.

Formerly known as Project Astoria, the ADO.NET Data Services defines a flexible addressing and query interface using a URL convention, and supports the usual resource manipulation methods for data sources, including the full range of Create, Read, Update, and Delete operations.

Microsoft Visual Studio 2008 SP1 and the upcoming Visual Studio 2010 fully support ADO.NET Data Services, including the capability to create and consume data services directly from the development environment.

You can find all the technical details of this announcement on the Interoperability team blog here, as well as on the Noelis blog. You can also find a tutorial on this here.

Announcing the PHP SDK for Windows Azure

Peter Galli — Wed, 13 May 2009 00:29:00 GMT

Vijay Rajagopalan, a Principal Architect here at Microsoft, is at TechEd India, where he will demo later this week a new set of interoperability projects related to PHP.

These projects include the PHP SDK for Windows Azure, an open source effort for which Microsoft has provided funding, with development by RealDolmen, whose goal is to provide high-level abstractions that enable PHP developers to interoperate readily with Windows Azure.

The PHP SDK for Windows Azure focuses on REST and provides PHP classes for Windows Azure blobs, tables and queue, helper classes for HTTP transport, AuthN/AuthZ, REST and error management, as well as manageability, instrumentation and logging support.

Rajagopalan will also announce the launch of a series of projects that offer samples and a toolkit that enable PHP developers to include Silverlight controls, Microsoft Virtual Earth maps and IE Webslices and Accelerators in PHP web applications; as well as automatically generated a simple "Create, Read, Update, Delete (CRUD)" PHP application from a table in SQL Server.

These projects, for which Microsoft has provided funding and which are available on Codeplex under a BSD license, are yet another proofpoint of the company's commitment to interoperability, and developers will be happy to know that the first batch of these have already been developed by Accenture.

Read Rajagopalan's full blog here for all the details.

The Azure Services Platform has been designed to be open, standards-based and interoperable, and its support for XML, REST and SOAP standards means that any of the Azure services can be called from other platforms and programming languages.

Microsoft has provided funding for two other SDKs that support third party programming languages: Java SDK for Microsoft .NET Services and Ruby SDK for Microsoft .NET Services so as to facilitate interoperability between the Azure Services Platform and non-Microsoft languages and technologies.

The inclusion of FastCGI in Windows Azure's hosting environment was announced at MIX 2009, and the protocol enables developers to run web applications on Windows Azure that were written using third party programming languages, including PHP. This opens up new options for PHP developers to deploy their applications.

A Technology Preview of the PHP SDK for Windows Azure will be released under a BSD license, while a functionally complete version of the SDK, which will support tables and queues, should be available for download by this fall of 2009, but the team is calling on developers to provide feature requests, test the toolkit, and join the user forum.

So, stay tuned, as there's a whole lot more to come!

Apache Stonehenge: Interoperability at Work

Peter Galli — Tue, 12 May 2009 17:24:00 GMT

The Stonehenge incubator project is approaching its first milestone: deploying the first set of samples and making them work together.

This is a really exciting development and continues to deliver on the project's primary goal: to provide practical applications that span languages and platforms and demonstrate how to achieve interoperability.

Multiple implementations of the Stonehenge Stocktrader sample application, including .NET, Java, PHP, Python and Ruby, have been committed to the repository. You can check the code here.

From a simplified architecture point of view, the Stonehenge Stocktrader application is built as follows:

A User Interface layer delivering the web front end (HTML)

A middle tier layer including a Business Services layer (login, account processing) and an Order Processing layer (buy/sell transactions)

A Data Access layer to provide access to the database for the middle tier layer (Business Services and Order Processing)

And, finally, the database where the application data lives

The work thus far has focused on the .NET, PHP, and Java interoperability scenarios, and the three Stocktrader implementations have been deployed in multiple configurations.

A series of tests were then run, mixing and matching the layers from the three implementations, playing with the configurations and leveraging the Web Services standards, including WS-Security, to provide message integrity and security.

A detailed "interoperability walkthrough" explaining all the different configurations has been posted here, while the full blog post by Kamaljit Bath, a Principal Program Manager in the Interoperability Technical Strategy Team at Microsoft, can be found here.

"Microsoft is pleased with its participation and the progress so far, and this new outcome from the Stonehenge project is very encouraging. With the implementation of the WS-* Standards, we get the benefit of distributed applications and platforms. We recognized that it is not always easy to achieve these goals, but I really feel this type of practical guidance will be helpful for these types of scenarios," said Bath.

The team is also actively soliciting comments and feedback, and encouraging both developers and users to participate in the project to ensure that the project continues to move in a direction that meets real people's needs.

ECMAScript Candidate Specification Published

Peter Galli — Fri, 10 Apr 2009 19:50:00 GMT

The candidate specification of the ECMAScript language standard - known as ECMA-262, was published on April 9.

ECMAScript is the scripting language used to create web pages with dynamic behavior, and is more commonly known as JavaScript. It is a component of every web browser and is an essential aspect of interoperability.

The ECMAScript standard is "one of the core standards that enable the existence of interoperable web applications on the World Wide Web," Ecma International, which develops standards for Information and Communication Technology, said in a media release.

This candidate specification, the PDF of which is available here, will now undergo interoperability and web compatibility testing, and will likely be submitted to the Ecma General Assembly for ratification as an Ecma standard before the end of 2009.

ECMA is inviting technical experts to review this candidate specification and submit feedback here by July 15, 2009.

This latest revision of ECMA-262 will now be known as ECMAScript, Fifth Edition and not under the previous working name ECMAScript 3.1.

The Fifth Edition codifies de facto interpretations of the language specification that have become common among browser implementations and adds support for new features, ECMA said.

The ECMAScript, Fifth Edition candidate specification has been developed by Ecma TC39, whose membership includes all major browser vendors.

These members will now create and test implementations of the candidate specification to verify its correctness and the feasibility of creating interoperable implementations and for web compatibility testing to ensure that the revised specification remains compatible with existing web applications.

TC39 members Opera, Mozilla, and Microsoft have each committed to participating in this testing process, which should be finished by the middle of July, and that a final draft of the specification can be agreed upon in September for submission to the Ecma General Assembly for final approval in December 2009.

ECMA also expects this to result in a fast-track submission to ISO/IEC JTC 1 for revision of ISO/IEC 16262.

"We expect the Fifth Edition to benefit all web developers by helping improve browser interoperability and making enhanced scripting features broadly available," said Allen Wirfs-Brock, Microsoft's ECMAScript architect. Read more about all this on Microsoft's JScript team blog.

The last major revision of the ECMAScript standard was the Third Edition, published in 1999 and work on future ECMAScript editions continues as part of the ECMAScript Harmony project.

Better Windows Development Environments - One project at a Time

Mark Stone — Fri, 10 Apr 2009 14:45:00 GMT

Discussions of the PC market usually break down into "desktop" vs. "server", as if these are the only platform categories. However, the developer's dev box -- call it a "workstation" to distinguish it from desktop -- is really a separate platform. Remember, when Linus Torvalds created Linux it wasn't because he needed a better
desktop operating system, or a better server operating system. What he wanted was something that could run the gcc compiler. He wanted a developer workstation he could use at home.

Of course the developer workstation market influences other markets. Developers who develop on a platform are more likely to develop for a platform. So winning developer mind share is often about giving them what they want in the way of development environment. And in this regard, open source developers are something of a
different breed.

Microsoft has a great set of developer tools; I've certainly known developers who swear by Visual Studio. But there's something of a disconnect between graphical tools favored by Windows developers and then command line tools favored by traditional open source developers; I've also known developers whose first order of business
with a new Windows workstation is to GNU-ify it.

Ironically, the Internet has a convergence effect, drawing these two camps together. Put developers online, and they can collaborate. Put developers online, and they can not only develop, but they can build, deploy, and test. The workstation has become not so much a computer as an environment. The developer's toolkit includes version control, build management, automated testing, and the need to do all these things as a team rather than an individual. Developer environments have evolved rapidly to adapt to these changes.

The Apache Software Foundation (ASF) seems to understand this evolution as well as anyone, and a number of ASF projects focus specifically on tools for the developer environment (Ant, Buildr, Continuum, Gump, and Maven come to mind as a few examples).

What's interesting is to see the .NET developers following suit, and wanting these same sorts of tools for their development environment. What's surprising is that this .NET effort is very grass roots driven.

"Panday" is a Filipino word meaning "blacksmith", and can also be a reference to the graphic novel super hero of the same name (the graphic novel is also originates from the Philippines). This provides an appropriate metaphor for the name of the NPanday project on Codeplex.

The NPanday project is one of several affiliated with Microsoft's Open Source Lab in the Philippines, and is part of the effort to bring to .NET some of the capabilities found in other open source development environments. The aim of NPanday is integrate Apache Maven into the .NET development environment.This would enable .NET
developers to take advantage of Maven-compatible development infrastructure.

Projects like NPanday are important because they offer developers more choice of tools in a Windows development environment. The more familiar those tools are to open source developers, the more open source development will be done on and for Windows. NPanday is also an important project for interoperability, making it easier to integrate .NET development with other development done using Maven.

Web Sandbox Source Now Available Under Apache License 2.0

Peter Galli — Tue, 27 Jan 2009 02:48:00 GMT

Microsoft has released more source code under an OSI-approved license: this time it has made the source code for the Web Sandbox runtime available under the Apache 2.0 open source license.

The Web Sandbox project explores how to advance the web platform to improve security, isolation, quality of service and extensibility capabilities for web developers and website users.

More information on the licensing details, as well as comprehensive documentation for experimenting and integrating with the Web Sandbox, can be found here.

But, while developers are being encouraged to help define and refine the Web Sandbox, it is not recommended for those developers creating production sites as it is still under development.

The Web Sandbox was created in response to limitations found in the current web platform, and is designed to explore potential solutions. Having a more secure and robust architecture as a foundational building block will help drive the next wave of Web innovation.

The Sandbox is a framework that works on most modern browsers that support the"ECMA-262, 3^rd Edition" (JavaScript) standard, and provides the same features in all modern web browsers. No browser add-ons or changes are required to leverage this technology. Beyond security, the Web Sandbox normalizes the different browsers and provides consistent W3C DOM support.

Since the initial release of Web Sandbox at PDC 2008, the team has received a lot of useful feedback from the web security community, and has also been collaborating with a number of customers, partners and the standards communities, all of whom want to adopt the technology when it is ready.

The goal? An open and interoperable standard that will help foster interoperability with complementary technologies like script frameworks and drive widespread adoption of the Web Sandbox.

This move is good news for Microsoft and the open source communities. But, it is important to note that while an Apache license is being used, the Web Sandbox project is not an Apache Software Foundation project and is not sponsored or endorsed by the ASF.

Microsoft does, however, already have an active relationship with the ASF. In fact, last year the company announced it had become a sponsor of the ASF so as to help enable the Foundation pay administrators and other support staff so that its developers can focus on writing great software.

Sam Ramji, the senior Director of Platform Strategy at Microsoft, also delivered a keynote address at ApacheCon in New Orleans last November.

Microsoft's Interoperability Technical Strategy Team already participates as a code contributor to the Apache Stonehenge incubator project; the company has also contributed a patch to ADOdb, a popular data access layer for PHP used by many applications and which is licensed under the LGPL and BSD; while Microsoft's Powerset team contributes to HBase, an open-source, column-oriented, distributed database written in Java.

Opening Day: Azure Platform Debuts

Sam Ramji — Mon, 27 Oct 2008 14:00:00 GMT

Today at PDC in Los Angeles, Ray Ozzie unveiled the Azure Services Platform, which will enable developers to build the next generation of applications - spanning all the way from the cloud to the enterprise data center. My team's focus has been on making sure that this platform treats open source development technologies as first-class citizens.

A key components of the Azure Services Platform is Windows Azure, an infrastructure that provides core capabilities such as virtualized computation, scalable storage, and automated service management. Developers will be able to build or extend parts or complete service-based applications using Live Services, .Net Services and SQL Services.

They will also be able to choose from a range of open source development tools and technologies, and be able to access Azure services using a variety of common internet standards, including HTTP, REST, WS* and Atom.

The Azure platform's goal is to support all developers and their choice of IDE, language and technology. We are also providing programmable components that can be consumed by other applications, and Microsoft is funding and sponsoring open source software development kits to enable Java and Ruby developers to take advantage of Azure.

This is significant as this is the first time we are delivering cross-platform software development kits at the same time as Microsoft Developer Network software development kits.

We are also funding these open source projects, under the BSD licensing model, in collaboration with Thoughtworks Inc. and Schakra Inc., and they will be run on open source portals RubyForge and SourceForge.

Much of this interoperability work was undertaken by Jean Paoli, the General Manager for Interoperability Strategy, and his team, including Vijay Rajagopalan, the Principal Architect for Interoperability Strategy, so a big thanks is due to them on this front.

In addition, as part of Microsoft's commitment to openness and working with open source communities, I asked the Open Source Technology Center (led by Tom Hanrahan) to come up with some specific examples that show how open source communities can access Windows Azure.

This work has allowed us to deliver several ‘proofs of concept' which show open source developers that they can create applications that run as services and have access to services in the cloud. These ‘proofs of concept' demonstrate that:

A developer using the Eclipse IDE can write a C# application that runs on Windows Azure
Gallery, the leading PHP photo application, can access Windows Azure cloud storage
A blog engine hosted on Windows Azure can authenticate users with OpenID.

Specific to Gallery, we've done two simple things: we created wrappers to convert the Windows Azure API to PHP objects, and we created a Windows Azure subclass inherited from the Windows NT Platform class. The net of all this is that, with a small amount of code, we were able to connect one of the top PHP application to Windows Azure, specifically, photo images stored as BLOBs in the cloud.

Finally, Microsoft is also going to publish the "M" language specification, including MSchema, MGrammar and MGraph, under the Open Specification Promise. This will facilitate the interoperability of the "Oslo" declarative modeling language, codenamed "M," with prominent industry standards such as WS* specifications, XML formats, industry protocols and security standards.

Stay tuned, because there's more to come.

Cheers,

Sam

Microsoft at AJAXWorld

Peter Galli — Mon, 20 Oct 2008 22:05:00 GMT

The AJAXWorld Conference and Expo got underway in San Jose today, under the broad theme of "Rich Web Technologies for Enterprise Web 2.0 & Social Web."

Scott Guthrie, a corporate vice president at Microsoft, delivered the keynote address today, while Brad Abrams, the Product Unit Manager for the AppFx team here at Microsoft, will also be presenting a couple of sessions over the next few days.

While Microsoft is not announcing anything new at the show, Abrams will point to the cumulative effect of all the work that has been done so far. He will talk about how JQuery will ship with future versions of Visual Studio, as well as how standards based JavaScript, CSS, and HTML are all now supported in Visual Studio 2008.

Attendees will also get to see how JQuery interoperability and usage is now on the same page with ASP.NET Ajax, as well as demos of the cross-browser, cross-platform Silverlight plug-in, which works on Firefox, Safari and Internet Explorer, and on both Macs and Windows machines.

Abrams tells me he also plans to show off a couple of Silverlight sites running on Linux with the Novell Moonlight implementation of Silverlight, as well as a demo of its Silverlight tools for Eclipse, which underscores how developers can use the tools they want to leverage Silverlight.

He has also posted a lot more detail on his talk, which was titled "Building a Great Ajax application from Scratch," in this blog post.

Also, Bryan Kirschner of the platform strategy group, will be delivering a keynote address on how Microsoft participates in a world of choice at GOSCON, the Government Open Source Conference, in Portland tomorrow.

In addition, two other colleagues from Microsoft will also be participating. Stuart McKee, the National Technology Office for the U.S., will be on the Government Open Collaboratives Panel with Brian, and Kathleen Connor from Microsoft's Health Solutions Group, will also be speaking.