I am happy to report that today the Advanced Message Queuing Protocol (AMQP) Working Group announced the availability of the AMQP 1.0 specification.
I am in New York attending the fourth annual AMQP business messaging conference and launch event for this important milestone, and Microsoft is thrilled to have been able to participate in the work to get the specification to this point.
As an open, interoperable, high-performance messaging protocol, AMQP opens up new possibilities in communications that span the client to the cloud, and will provide customers with increased choice.
AMQP has been developed over the years through the collective work of the 24 companies - and the many diverse communities they represent - that constitute the AMQP Working Group, including JP Morgan, VMware, Red Hat, Deutsche Borse Group, Microsoft, INETCO Systems, Goldman Sachs, and WS02.
These WG members are all committed to working together on open standards and represent a diverse range of communities, many of them Open Source.
Microsoft has been a member of the AMQP WG since 2008 and we have actively contributed to the development and testing of the protocol.
We are also supportive of, and excited about, the transition of the AMQP work to OASIS, a consortium whose goal is to advance open standards, and the subsequent standardization of AMQP 1.0, which is an important first step towards wider adoption of the specification.
Microsoft supports thousands of standards in its products and we actively participate in more than 150 standards organizations and over 350 working groups worldwide. We will continue to participate actively in these standards bodies, contributing to the development of new open standards and the improvement of existing standards.
We recognize that no single company can address interoperability challenges on its own and that collaboration with customers, partners, open source communities and other vendors is of critical importance. This collaboration includes open communication on the interoperability challenges that customers are experiencing and the ways in which those challenges can be addressed.
Openness and interoperability are important to Microsoft, our customers, partners, and developers, and AMQP has the potential to improve interoperability between various vendor products, which is extremely important to our customers.
Technical Diplomat: Microsoft's Interoperability Group
[Cross-posted on the Windows Phone Developer Blog]
Windows Phone 7.5 “Mango” is just out of the door, smoothly going to users’ phones. So, if you or your friends haven’t started to look at Windows Phone, this is great timing.
Today I’m excited to announce new guidance based on migration samples and a SQLite to SQL Server Compact database conversion tool. We hope that these new items combined with our previous extensive guides (for Android, iPhone, and Symbian Qt) will accelerate your ramp up time and improve your experience in porting apps to Windows Phone from iPhone and Android. Read below to see what we’ve got for you.
First we have built a series of samples to aid you in the process of migrating your iPhone & Android applications over to Windows Phone by providing a look at the differences and similarities of each platform. Through analysis, you'll see how to implement the same functionality on Windows Phone as you have within your iPhone and Android application. We’ve started with 3 samples:
And for each sample, you’ll find the source code on Android/iPhone, the Windows Phone ported version and the porting notes. The content is available here for Android, and here for iPhone. And since we had a little bit of extra time, we added a bonus track for Android developers, with a “10 simple tasks: tips & tricks” article, where we explain how common simple tasks performed during Android development can be done when doing Windows Phone development.
Finally, we also included a sample “Notification Service”, which shows how to build a multiplatform push-notification services supporting the different providers used by Android, iPhone and Windows Phone. Documentation is available here and sample code is here.
Windows Phone 7.5 “Mango” includes relational database support by way of Microsoft SQL Server Compact (SQLCE). So we thought it might be handy to create a tool to aid developers in getting their database (data, schemas and views) ported over to Windows Phone without too much trouble. Differences in data types between various database platforms can make the manual migration of your data a daunting task. SQLite2SQLCE is a tool developed to make the conversion process simple by converting a SQLite database into SQLCE while simultaneously creating the default classes needed to incorporate the new database into your Windows Phone application.
With the database conversion tool, we’ve also included a nifty tool designed to aid developers in converting their SQL queries to LINQ while simultaneously helping them to learn the new query language. LINQ (Language-Integrated Query) is a native data querying toolset integrated into the .NET Framework and use on Windows Phone.
Documentation and a simple migration sample are available here. And by the way, the source code of these utilities is available on CodePlex.
The API Mapping tool has been expanded: it now covers a few more features like sensors (Camera, Compass & Gyro), multitasking (notification, app switching & background agents) , data access (SQL, file access), launchers/choosers. The API Mapping tool is available here: http://wp7mapping.interoperabilitybridges.com/
Finally, once you’ve be through all our “Porting” guidance, I recommend that you follow at your own pace the “Window Phone Mango Jump Start” online video training.
We encourage developers to leave comments and questions on any article. We are watching and we are open to feedback. If you see something missing or want to suggest new API mapping or porting topic to include just go to http://wp7mapping.uservoice.com.
More good news on Microsoft's commitment to Interoperability in the cloud: last week Sandy Gupta, the General Manager for Microsoft's Open Solutions Group, announced that Windows Server Hyper-V is now an officially supported hypervisor for OpenNebula.
This open source project is working on a prototype for release next month and it will soon be possible for customers to build and manage OpenNebula clouds on a Hyper-V based virtualization platform.
"Windows Server Hyper-V is an enterprise class virtualization platform that is getting rapidly and widely deployed in the industry. Given the highly heterogeneous environments in today’s data centers and clouds, we are seeing enablement of various Linux distributions including SUSE, CentOS, Red Hat, and CS2C on Windows Server Hyper-V, as well as emerging open source cloud projects like OpenStack -- and now OpenNebula," Gupta said in a blog post.
Are you a Web developer, designer or just interested in the space? Well, if you are, you really don’t want to miss W3Conf.
W3Conf is the W3C's first ever 2-day conference for developers and designers, and is uniquely focused on cutting edge technologies that work today across browsers.
It is being held in Redmond, Washington November 15-16 2011 and it’s packed with top-notch presentations by leading experts in the Web industry on HTML5, CSS3, graphics, accessibility, multimedia, APIs and more.
I’m participating in the “Browsers and Standards: Where the Rubber Hits the Road” panel discussion, along with Tantek Çelik from Mozilla, Google’s Chris Wilson and Divya Manian from Opera.
Microsoft is proud to be the host sponsor of the event, joined by AT&T, Adobe, and Nokia.
There are several ways to experience this conference: you can register to attend in person; videos of the presentations (with English captioning) will be streamed live over the Web; and recordings will be archived and made freely available for future reference. Note that the Early Bird registration conference and hotel discount expires on October 31.
You can find all the details on the schedule, speakers, and the technologies themselves on the conference web site, which demonstrates the features enabled in modern browsers and authoring tools to make attractive, interactive, and accessible websites using emerging standards from W3C and other bodies. In other words, the site itself “eats the open web dog food.”
Along with my colleagues on the Interoperability Team, I believe this will be a great event, and encourage you to attend virtually or in person.
I look forward to seeing you there!
Co-Chair: HTML Working Group