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

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

Silverlight 4 Beta Hits the Street

Peter Galli — Wed, 18 Nov 2009 17:59:00 GMT

The beta for Silverlight 4 was released today, Scott Guthrie, a Corporate Vice President in Microsoft's Developer Division, told attendees at the annual Professional Developers Conference here in Los Angeles.

The final verison of the product will be shipped in the first half of 2010, he said, noting that the release of the beta means that developers can begin testing the capabilities of Silverlight 4 to plan for the great applications and rich, compelling user experiences to come, both on and off the Web.

Some 90% of the most commonly requested features were incorporated into Silverlight 4, which is currently installed on 40% of all internet devices and more than 50% of US broadband PCs, Guthrie said.

A number of customers, including Snapflow, Seesmic and H&R Block, as well as numerous Microsoft properties such as Xbox, Bing and MSN, are all already using Silverlight to create compelling user experiences.

The Silverlight 4 beta extends beyond the browser, and brings new out-of-browser capabilities, enabling new experiences that reach deeper into the desktop without additional code or runtimes required.

Webcam and microphone with local recording capability opens new possibilities for innovative interactive media experiences, while native multicast support enables efficient enterprise-wide training and internal communications behind the firewall.

Full support for Silverlight in Visual Studio 2010 gives enterprise developers a tried and trusted development environment and languages that scales for mission-critical enterprise scenarios, while integration with Microsoft Office and Microsoft SharePoint bring the benefits of Silverlight interactivity to a broad enterprise install base, Guthrie said.

Enhanced printing, networking, databinding, reporting and charting capabilities satisfy common business needs, while Silverlight has a growing library of over 60 customizable controls to create rich, interactive applications to rapidly build attractive, functional business applications.

Microsoft also has extended support for Google's Chrome browser with Silverlight 4.

Microsoft is also working with the open source community to ensure that Silverlight content is available to them. Earlier this year, Moonlight 1.0 was released. Moonlight is an open source project that gives Linux users access to Microsoft Silverlight content, and is available for all major Linux distributions, including openSUSE, SUSE Linux Enterprise, Fedora, Red Hat, and Ubuntu.

PDC 2009: Availability of the Windows Azure Platform

Peter Galli — Tue, 17 Nov 2009 18:14:00 GMT

Ray Ozzie, Microsoft's Chief Software Architect, used the company's annual Professional Developers Conference here in Los Angeles to announce the availability of the Windows Azure platform.

That platform consists of Windows Azure, the operating system as-a-service, and SQL Azure, a fully relational database in the cloud. The Service Bus and Access Control services, formerly known as the .NET Services, now run directly within Windows Azure and are known as Windows Azure platform AppFabric Service.

Microsoft will continue to offer Windows Azure as a Community Technology Preview until the end of this year, after which it will switch to a production service under which Azure's cloud services will be made available to enterprises. But users will get a fee pass in January, since charges will only start accruing in February.

In his opening keynote, Ozzie also announced that a small number of customers will go into production today, including Automattic, Inc., the maker of WordPress, which is now live on Azure. Matt Mullenweg, founder of Automattic, Inc., took the stage to demonstrate MySQL, PHP, and Apache support on Windows Azure, as well as to announce that his company is launching a new site that runs on SQL Azure.

Ozzie also used his keynote to made clear that reaching all developers was top of mind for Microsoft.

"To most developers, to developers like you, Windows Azure appears as a model based extension to Visual Studio, enabling you to build apps that leverage your skills in SQL, IIS, ASP.NET, and .NET Framework. Alternatively, and of course it's your choice, you might leverage your skills by using MySQL and PHP within Azure, or you might instead take advantage of our new Azure tools for Java and Eclipse. Reaching all developers is incredibly important to us," he said.

Windows Azure now supported any kind of Windows code and programming model, and any kind of multi-role, multi-tier service design pattern, supporting extremely flexible binding and arbitrary relationships between roles, Ozzie said.

"Because you wanted it, we've broadened far beyond just the .NET programming model, and the Web role, worker role service design pattern. We added support for FastCGI, enabling high scale Web apps to be written in any of a variety of programming languages. And, in sessions this week, you're going to see the Windows Azure team quickly building and deploying Java apps, running under Tomcat. You'll see PHP apps under MySQL," he said.

Earlier this year, Microsoft enabled .NET full trust and native code applications. This functionality allowed developers to spawn xcopy deployable processes. As a result, Java applications can now be packaged and run.

Today, we announced that we are delivering a solution accelerator for Tomcat, an open source software implementation of the Java Servlet and JavaServer Pages technologies, as well as launching a Java SDK for Windows Azure Storage (tables, blogs, and queues). External endpoints (inbound traffic) to worker roles have also been enabled, which enables applications that receive internet traffic that aren't running under IIS.

During his keynote Ozzie also introduced Vivek Kundra, the Federal Chief Information Officer at the White House, who spoke via live feed from Washington D.C., and who encouraged developers to take advantage of the vast amount of public data to create applications using this new Microsoft technology.

"I'm really excited about what NASA is doing in cooperation with Microsoft with the launch of the Pathfinder Innovation Challenge ... anybody can participate and look at the data that has been democratized through NASA on the Azure platform, that allows people to look around the red planet, slice and dice, and cube, and create information, and advance our understanding of the universe," Kundra said.

This commitment to all developers is not new. When Ozzie first announced the Windows Azure platform at PDC last year, Sam Ramji blogged that developers 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," he said.

And, earlier this year, Microsoft introduced 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.

Next up at PDC 2009 was Bob Muglia, President of Microsoft's Server and Tools Business, who noted that Microsoft is converging on a common developer platform for both servers and services, that will enable developers to continue using familiar .NET Framework and Visual Studio tools and technologies, as well as third party tools such as Eclipse, to create and monetize applications that run on the server and as services in the cloud.

Muglia also announced the company's plan to offer Windows Server Virtual Machine support on Windows Azure, enabling customers to more easily support virtualized infrastructure across the continuum of on premises and cloud computing.

In addition, Muglia announced the new release of ASP.NET MVC beta 2, a free, fully-supported framework that enables developers to rapidly build standards-based Web applications through rich AJAX integration and enhanced extensibility.

In other related news, SugarCRM, a provider of commercial open source customer relationship management software, today also announced that it will offer its CRM applications on Windows Azure to enable its customers and value-added resellers to benefit from the real-time scalability, high availability and on-demand infrastructure of Azure.

"With Windows Azure, Microsoft has built a true cloud computing platform going well beyond the simple hosted infrastructure that most service providers offer today. Windows Azure enables SugarCRM value-added resellers to create and deploy unique solutions for customers around the globe. This new service is another key component of the Sugar Open Cloud, the SugarCRM cloud strategy for delivering simple, affordable CRM anywhere based on customer need," said Larry Augustin, CEO of SugarCRM, in a press statement.

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.

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.

Brazilian Students Set Their Own Course

Mark Stone — Mon, 16 Mar 2009 19:05:00 GMT

I’m going to tell a story that starts in Indiana, but really it’s about Brazil.

Once upon a time “scientific computing” was nearly synonymous with “Fortran”. Today, though, just about any high level language can be used to write High Performance Computing (HPC) applications. These days that language choice also includes C#.

At Indiana University, the Open Systems Lab has pioneered work to implement Message Passing Interface (MPI) support for .Net, so that MPI applications can be written in C#. The project is MPI.Net, and you can find it on Codeplex. It is open source, about three years old, has reached a 1.0 release, and is compatible with two other important open source projects, OpenMPI and Mono. The principle developers behind the project are Andrew Lumsdaine at Indiana University and his former student, Douglas Gregor, who is now on the faculty of Rensselear Polytechnic Institute.

This is the kind of open source work that’s really exciting to see because of the way it expands choices for the developer and the end user. A C# developer should not be closed off from writing HPC applications if that’s what they want to do. And a research scientist should not have to think about whether their lab is running Linux or Windows Server. Both of these individuals are working enough layers above the operating system that somebody else’s operating system choice should not be a constraint.

So I was very excited to learn that students in Brazil at Federal University of Rio Grande do Sul were doing work on MPI, and excited to talk with them about their work. One of their projects is MPI#, also open source and also hosted on Codeplex.

MPI# builds on top of the work of MPI.Net, adding some functionality not yet present in MPI.Net. Specifically, quoting from the project description:

The goals of this project would be to build upon MPI.NET in order to complement it with the features that are missing, mainly regarding collective communication. Either they could benefit from C# native support for such communication, either they could be programmed on top of the provided MPISend/MPIRecv encapsulations. C# and .NET features such as fault tolerance or dynamicity support would be studied, in other to turn the MPI# implementation robust in large, dynamic and heterogeneous platforms.

Two of the students working on MPI# are Ismael Stangherlini and Fernando Afonso. They are graduate students in computer science, working on projects affiliated with the Brazilian Interoperability and Open Source Software Development Nucleous. When I talked to them about their work on MPI# I was curious what their communication with Indiana University had been like. Their response: they had never been in contact with Indiana University; they simply downloaded the code for MPI.Net and started working on their own.

That’s the magic of open source: that they can, in fact, just download the code on their own and start coding against it. They may make an important contribution to MPI.Net. Or their code may be entirely disregarded. Or they may move on to other projects and somebody else may or may not pick up where they left off. At this stage it’s too early to tell. But the fact that all of these scenarios are possible demonstrates why, as a methodology, open source is so nimble and adaptive. A top-down product development process, or a top-down standards development process can only execute on the innovations envisioned by the few at the top, and at the speed of the slowest decision-makers in the process. But a bottom-up open source process enables every innovation that anyone at the grass roots level can see.

SMB2: a Complete Redesign of the Main Remote File Protocol for Windows

Peter Galli — Mon, 08 Dec 2008 16:24:00 GMT

SMB (Server Message Block) is a remote file protocol commonly used by Microsoft Windows clients and servers that dates back to 1980's.

Back when it was first used, LANs speeds were typically 10Mbps or less, WAN use was very limited and there were no Wireless LANs. Network security concerns like preventing man-in-the-middle attacks were non-existent at that time.

Obviously, things have changed a lot since then. SMB did evolve over time, but it did so incrementally and with great care for keeping backward compatibility. It was only with SMB2 in 2007 that we had the first major redesign.

In this blog Jose Barreto, a senior technical evangelist in Microsoft's Storage Solutions Division, explains some of the history behind the protocol and outlines important improvements in SMB2, particularly in regards to reduced complexity, pipelining and compounding.

Introduction

SMB (Server Message Block) is a remote file protocol commonly used by Microsoft Windows clients and servers that dates back to 1980's. Back when it was first used, LANs speeds were typically 10Mbps or less, WAN use was very limited and there were no Wireless LANs. Network security concerns like preventing man-in-the-middle attacks were non-existent at that time. Obviously, things have changed a lot since then. SMB did evolve over time, but it did so incrementally and with great care for keeping backward compatibility. It was only with SMB2 in 2007 that we had the first major redesign.

A History of SMB and CIFS

When it was first introduced to the public, the remote file protocol was called SMB (Server Message Block). SMB was used, for instance, by Microsoft LAN Manager in 1987 and by Windows for Workgroups in 1992. Later, a draft specification was submitted to the IETF under the name Common Internet File System (CIFS). The CIFS specification is a description of the protocol as it was implemented in 1996 as part of Microsoft Windows NT 4.0. A preliminary draft of the IETF CIFS 1.0 specification was published in 1997. Later, extensions were made to address other scenarios like domains, Kerberos, shadow copy, server to server copy and SMB signing. Windows 2000 (released in 2000) included those extensions. At that time, some people went back to calling the protocol SMB once again. CIFS/SMB has also been implemented on Unix, Linux and many other operating systems (either as part of the OS or as a server suite like Samba). A few times, those communities also extended the CIFS/SMB protocol to address their own specific requirements.

One important limitation of SMB was its "chattiness" and lack of concern for network latency. It would take a series of synchronous round trips to accomplish many of the most common tasks. The protocol was not created with WAN or high-latency networks in mind and there was limited use of compounding (combining multiple commands in a single network packet) or pipelining (sending additional commands before the answer to a previous command arrives). This even led to products created to address the specific issues around SMB WAN acceleration. There were also limitations regarding the number of open files, shares and users. Due to the large number of commands and subcommands, the protocol was also difficult to extend, maintain and secure.

Introducing SMB2

The first major redesign of SMB happened with the release of SMB2 by Microsoft. SMB2 was introduced with Windows Vista in 2007 and updated with the release of Windows Server 2008 and Windows Vista SP1 in 2008.

SMB2 brought a number of improvements, including but not limited to:

Reduced complexity, going from over 100 commands and subcommands to just 19 (see details below)
General mechanisms for data pipelining and credit-based flow control (see details below)
Request compounding, which allows multiple SMB requests to be sent as a single network request(see details below)
Larger reads and writes make better use of faster networks, even with high latency
Caching of folder and file properties, where clients keeps local copy of information on folders and files
Durable handles allow an SMB2 connection to transparently reconnect to the server if there is a temporary loss of network connectivity
Message signing improved (HMAC SHA-256 replaces MD5 as hashing algorithm) and configuration/interoperability issues simplified
Improved scalability for file sharing (number of users, shares and open files per server greatly increased)
Protocol works well with Network Address Translation (VC count is gone)
Extension mechanism (for instance, create context or variable offsets)
Support for symbolic links

It is important to highlight that, to ensure interoperability, SMB2 uses the existing SMB1 connection setup mechanisms, and then advertises that it is capable of a new version of the protocol. Because of that, if the opposite end does not support SMB2, SMB1 will be used.

The SMB2 protocol specification was published publicly by Microsoft and you can find the link at the end of this post.

Reduced Complexity

One of the ways to showcase the reduced complexity in SMB2 is to make a comparison to the commands and subcommands in the old version.

Here is the complete list of the 19 opcodes (or commands) used by SMB2 in the message exchanges between the client and the server, grouped in three categories:

Protocol negotiation, user authentication and share access (NEGOTIATE, SESSION_SETUP, LOGOFF, TREE_CONNECT, TREE_DISCONNECT)
File, directory and volume access (CANCEL, CHANGE_NOTIFY, CLOSE, CREATE, FLUSH, IOCTL, LOCK, QUERY_DIRECTORY, QUERY_INFO, READ, SET_INFO, WRITE)
Other (ECHO, OPLOCK_BREAK)

When you try to get a similar list for the old SMB, things get a little more complex. I tried to make a list of all commands and subcommands using only the documents linked below and came up with over 100:

Protocol negotiation, user authentication and share access (NEGOTIATE, SESSION_SETUP_ANDX, TRANS2_SESSION_SETUP, LOGOFF_ANDX, PROCESS_EXIT, TREE_CONNECT, TREE_CONNECT_ANDX, TREE_DISCONNECT)
File, directory and volume access (CHECK_DIRECTORY, CLOSE, CLOSE_PRINT_FILE, COPY, CREATE, CREATE_DIRECTORY, CREATE_NEW, CREATE_TEMPORARY, DELETE, DELETE_DIRECTORY, FIND_CLOSE, FIND_CLOSE2, FIND_UNIQUE, FLUSH, GET_PRINT_QUEUE, IOCTL, IOCTL_SECONDARY, LOCK_AND_READ, LOCK_BYTE_RANGE, LOCKING_ANDX, MOVE, NT_CANCEL, NT_CREATE_ANDX, NT_RENAME, NT_TRANSACT, NT_TRANSACT_CREATE, NT_TRANSACT_IOCTL, NT_TRANSACT_NOTIFY_CHANGE, NT_TRANSACT_QUERY_QUOTA, NT_TRANSACT_QUERY_SECURITY_DESC, NT_TRANSACT_RENAME, NT_TRANSACT_SECONDARY, NT_TRANSACT_SET_QUOTA, NT_TRANSACT_SET_SECURITY_DESC, OPEN, OPEN_ANDX, OPEN_PRINT_FILE, QUERY_INFORMATION, QUERY_INFORMATION_DISK, QUERY_INFORMATION2, READ, READ_ANDX, READ_BULK, READ_MPX, READ_RAW, RENAME, SEARCH, SEEK, SET_INFORMATION, SET_INFORMATION2, TRANS2_CREATE_DIRECTORY, TRANS2_FIND_FIRST2, TRANS2_FIND_NEXT2, TRANS2_FIND_NOTIFY_FIRST, TRANS2_FIND_NOTIFY_NEXT, TRANS2_FSCTL , TRANS2_GET_DFS_REFERRAL, TRANS2_IOCTL2, TRANS2_OPEN2, TRANS2_QUERY_FILE_INFORMATION, TRANS2_QUERY_FS_INFORMATION, TRANS2_QUERY_PATH_INFORMATION, TRANS2_QUERY_PATH_INFORMATION, TRANS2_REPORT_DFS_INCONSISTENCY, TRANS2_SET_FILE_INFORMATION, TRANS2_SET_FS_INFORMATION, TRANS2_SET_PATH_INFORMATION, TRANSACTION, TRANSACTION_SECONDARY, TRANSACTION2, TRANSACTION2_SECONDARY, UNLOCK_BYTE_RANGE, WRITE, WRITE_AND_CLOSE, WRITE_AND_UNLOCK, WRITE_ANDX, WRITE_BULK, WRITE_BULK_DATA, WRITE_COMPLETE, WRITE_MPX, WRITE_MPX_SECONDARY, WRITE_PRINT_FILE, WRITE_RAW)
Other (ECHO, TRANS_CALL_NMPIPE, TRANS_MAILSLOT_WRITE, TRANS_PEEK_NMPIPE, TRANS_QUERY_NMPIPE_INFO, TRANS_QUERY_NMPIPE_STATE, TRANS_RAW_READ_NMPIPE, TRANS_RAW_WRITE_NMPIPE, TRANS_READ_NMPIPE, TRANS_SET_NMPIPE_STATE, TRANS_TRANSACT_NMPIPE, TRANS_WAIT_NMPIPE, TRANS_WRITE_NMPIPE)

I make no claim that the list above for SMB is exact or complete, but it does make a point. As an interesting exercise, check the lists above to verify that, while SMB2 has a single WRITE operation, there are 14 distinct WRITE operations in the old protocol.

SMB2 also requires TCP as a transport. SMB2 no longer supports NetBIOS over IPX, NetBIOS over UDP or NetBEUI (as SMB version 1 did).

Pipelining

A key improvement in SMB2 is the way it makes it easy for clients to send a number of outstanding requests to a server. This allows the client to build a pipeline of requests instead of waiting for a response before sending the next request. This is especially relevant when using a high latency network.

SMB2 uses a credit based flow control, which allows the server to control a client's behavior. The server will start with a small number of credits and automatically scale up as needed. With this, the protocol can keep more data "in flight" and better utilize the available bandwidth.

This is key to make a large transfer go from hours (in SMB) to minutes (in SMB2) in a "long and fat pipe" (high bandwidth, high latency network).

For an example of how pipelining in SMB2 can improve performance, check out this blog post.

Compounding

When you look at the command set for the new SMB2 protocol, you notice that they are all simple operations. The old SMB1 protocol had some complex commands and subcommands that combined a set of simple operations as required in specific scenarios.

One of the important changes in SMB2 is the ability to send an arbitrary set of commands in a single request (single network round trip). This is called compounding and it can be use to mimic the old complex operations in SMB1 without the added complexity of a larger command set.

For instance, an old SMB1 RENAME command can be replaced by a single request in SMB2 that combines three commands: CREATE (which can create a new file or open an existing file), SET_INFO and CLOSE. The same can be done for many other complex SMB1 commands and subcommands like LOCK_AND_READ and WRITE_AND_UNLOCK.

This compounding ability in SMB2 is very flexible and the chain of commands can be unrelated (executed separately, potentially in parallel) or related (executed in sequence, with the output of one command available to the next). The responses can also be compounded or sent separately.

This new compounding feature in SMB2 can be used to perform a specific task in less time due to the reduced number of network round trips.

Conclusion

I hope this post has helped you understand some of the important improvements in SMB2, particularly in regards to reduced complexity, pipelining and compounding.

Reference

Below is a list of important links that document SMB2, SMB and CIFS, including the latest protocol specifications published by Microsoft: