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

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.

Microsoft to Open Source the .NET Micro Framework

Peter Galli — Mon, 16 Nov 2009 15:16:00 GMT

I have great news to announce. Today, at the Microsoft Professional Developer Conference (PDC) here in Los Angeles, we announced not only the release of version 4.0 of the.NET Micro Framework, but also that we are open sourcing the product and making it available under the Apache 2.0 license, which is already being used by the community within the embedded space.

The .NET Micro Framework,a development and execution environment for resource-constrained devices, was initially developed inside the Microsoft Startup Business Accelerator, but recently moved to the Developer Division so as to be more closely aligned with the overall direction of Microsoft development efforts.

The result of this is that the .NET Micro Framework has become a seamless development experience, bringing a single programming model and tool chain for the breadth of developer solutions, all the way from small intelligent devices, to servers and the cloud. There are also no more time-limited versions.

Including the source code for almost all of the product also ensures that developers now also get access to the Base Class Libraries that were implemented for .NET Micro Framework and the CLR code itself.

However, both the TCP/IP stack and Cryptography libraries are not included in the source code. Program Manager Colin Miller told me this was because the TCP/IP stack is third party software that Microsoft licenses from EBSNet, so we do not have the rights to distribute that source code. If someone needs to access the source code for the TCP/IP stack, they can contact EBSNet directly.

As for the Cyptography libraries, they are not included in source code because they are used outside of the scope of the .NET Micro Framework. Customers who need to have access to the code in the cryptography functions will find that these libraries can be replaced, Miller said.

I asked Miller what the future plans for the .Net Micro Framework were, and he made clear that Microsoft intends to remain actively involved in its ongoing development, working alongside the community. While the license will allow customers to take the code and make specialized versions to fit their needs, customers told us they wanted Microsoft to stay involved to avoid any possible fragmentation of the platform.

"As such, we are planning on establishing a core technology team that is made up of both Microsoft and non-Microsoft contributors that continues the goals of producing a high quality product for very small devices. This group will act as the gateway to community contributions while, at the same time, Microsoft Developers will continue add functionality and coordinate with the overall .NET team," he said.

Microsoft is also in the process of forming a community of interested and involved members to help shape the future direction of the product. There will be a core technology team that is composed of Microsoft and external partners, and people will be encouraged to propose projects, which will be vetted before they are accepted.

"The site will also support people building extensions that exist alongside the platform rather than being integrated into it, " Miller told me.

The PHP Toolkit for ADO.NET Data Services

Peter Galli — Fri, 21 Aug 2009 11:00:00 GMT

Today, the DPE Interop team at Microsoft released a new open source project that bridges PHP and .NET using REST.

Specifically, the PHP Toolkit for ADO.NET Data Services was made available, which makes it easier for PHP developers to take advantage of the ADO.NET Data Services, a set of features recently added to the .NET Framework.

The PHP Toolkit for ADO.NET Data Services is an open source project funded by Microsoft and developed by Persistent Systems. It is available on CodePlex today.

These services, which were previously referred to by the codename Project Astoria, expose a wide range of data sources through a RESTful service interface.

There is full support for ADO.NET Data Services in Visual Studio 2008 SP1 as well as in the upcoming Visual Studio 2010, which includes direct support for both creating and consuming data services directly from the development environment.

Read more about all this on the Interoperability blog, and watch the Channel 9 video interview with Claudio Caldato, Senior Program Manager in the Interoperability Technical Strategy team, and Pablo Castro, software architect of ADO.NET Data Services.

This is yet another example of Microsoft's continued commitment to openness and interoperability as well as of its embrace of Web standards in its technologies.

Moonlight 1.0 Hits the Street

Peter Galli — Wed, 11 Feb 2009 19:42:00 GMT

Moonlight 1.0 is now available.

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. This milestone release is part of the technical collaboration between Novell and Microsoft.

Microsoft has worked with the Moonlight team and Novell to enable interoperability between Windows and Linux platforms and extend the high-quality interactive Web and video experience for the benefit of the Linux community, said Scott Guthrie, corporate vice president of Microsoft's .NET Developer Division.

Microsoft has provided Novell with access to its test suites for Silverlight, and provides Linux end users of Moonlight with free access to the Microsoft Media Pack, a set of licensed media codecs for video and audio that bring optimized and licensed decoders to every Linux user using Moonlight. Windows Media Video (.wmv), Windows Media Audio (.wma) and MP3 files are supported through the Microsoft Media Pack.

A pre-release of Moonlight was made available on January 19, 2009 to allow Linux users to stream Barack Obama's Inauguration, and more than 20,000 Linux users downloaded Moonlight to watch that Silverlight broadcast.

"Microsoft Silverlight offers the most comprehensive and powerful solution for the creation and delivery of rich internet applications and media experiences, and is used by hundreds of thousands of developers worldwide," Guthrie said.

For his part Miguel de Icaza, the founder of the Mono project founder and vice president of Developer Platforms at Novell, said Moonlight brings the benefits of Silverlight's popular multimedia content to Linux viewers. "This first release delivers on the goal of breaking down barriers to multimedia content and creating parity in the user's viewing experience regardless of whether the user is on Windows or Linux."

DotNetNuke Moves to CodePlex

Peter Galli — Wed, 07 Jan 2009 22:31:00 GMT

DotNetNuke Corporation, the creator of the industry-leading DotNetNuke development framework, has decided to leverage the CodePlex infrastructure for its core product distribution.

DotNetNuke will utilize CodePlex for download infrastructure, bandwidth, and metrics reporting for its core product offerings. Until now, DotNetNuke had been leveraging services from SourceForge.Net. DotNetNuke is also currently the second most commonly downloaded project on CodePlex.

Last February, DotNetNuke Corporation announced the availability of the DotNetNuke Forge, the prime destination for open source collaboration on the DotNetNuke platform. The DotNetNuke Forge has grown in breadth and popularity over the past year and now represents a vital part of the DotNetNuke ecosystem.

The DotNetNuke Corporation researched the many open source project hosting services available, and decided that CodePlex provided the "most reliable and dependable infrastructure, cleanest user experience, most advanced project administration tools, and highest commitment to future innovation," said Scott Willhite, its Co-Founder and Community Director.

CodePlex Program Manager Sara Ford says Microsoft is excited about having DotNetNuke join the CodePlex community and, as the leading open source web application framework for ASP.NET, the CodePlex team is looking forward to partnering with them to promote open source development on the Microsoft platform.

The team is also looking forward to hearing the feedback from the DotNetNuke community for improving the open source development experience on CodePlex.

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:

BizSpark Program Targets Startups

Peter Galli — Tue, 04 Nov 2008 21:49:00 GMT

The extremely popular and well attended Web 2.0 Summit starts in San Francisco today, where Microsoft officially launched its global BizSpark program, designed to help startups grow into successful businesses through software support, a vibrant global ecosystem that delivers superior business advantage, and opportunities for visibility through a new online database, the BizSparkDB.

BizSpark is available globally to privately held startups that are building a software-based product or service, that have been in business less than three years, and have less than $1 million in revenue.

It also provides startups with software, support and visibility early in their life cycle when those resources are most needed and least affordable. As such, Microsoft has decided that the $100 program fee will be made payable when the company leaves the program rather than upfront when joining.

Under the program, startups will receive speedy, easy access to Microsoft's current full-featured development tools, platform technologies, and production licenses of server products. They can use these immediately to develop and bring innovative and interoperable solutions to market with no upfront costs and minimal requirements.

Startups will also receive professional support from Microsoft and BizSpark Network Partners around the world. Network Partners are incubators, investors, advisors, government agencies and hosters who are vested in software-fueled innovation and entrepreneurship.

BizSpark members will also be informed about those programs of particular interest to startups, including the Microsoft Web Platform Installer and Microsoft Web Application Installer.

These offerings make it easier for developers to bring PHP and .NET Web applications to market faster, with a streamlined download, install and configure experience, as well as design and development integration and pre-packaged open source applications that run well on the Microsoft Web Platform.

BizSpark members will also get access to the community technology preview of the Azure Services Platform, which was announced last month at the Microsoft Professional Developers Conference in Los Angeles.

Azure is a new computing platform that will help developers build the next generation of applications, spanning all the way from the cloud to the enterprise datacenter, while delivering new experiences across the PC, Web and phone.

They will also get access to the community technical preview of the Live Framework, a simple, open and interoperable framework for developers to access and consume Live Services, a set of building blocks within the Azure Services Platform for handling user data and application resources, which includes Live Mesh technologies for synchronizing users' data and extending Web applications across multiple devices.

The BizSpark program is a really positive move, since most startups pretty much always needs help, even in the best of times. In times of economic hardship, they need all the help they can get, so they can deliver on their promise of great software innovation and job creation. Microsoft is doing its part to make sure that happens.