1. Windows DNA: The Microsoft Application Platform for the Enterprise
Carlos McKinley
Microsoft Corporation

2. Agenda
DNA Explored
Site Server
XML & BizTalk Server
Web Services

3. Evolution To Web Services
XML
Programmability
Connectivity
HTML
Presentation
TCP/IP
Technology
Innovation
FTP, , Gopher
Web Pages
Browse the Web
Program the Web
Web Services
TCP/IP: universal protocol
HTML: universal presentation
XML: universal description
You’ve seen this slide before, no doubt, but to recap:
TCP/IP has basically ended the network protocol wars of the ’80s and early 90’s. The resulting connectivity allows devices of all kinds to talk to each other all over the world.
HTML provided a similar standard for the presentation of text and graphical information on the Web.
Both TCP/IP and HTML are very simple technologies. There’s another simple technology that’s going to make an equally revolutionary change to the Internet: XML.
XML is a way of describing what the data means; this as contrasted with HTML, which describes how the data looks.
Just as HTML was a catalyst for information presentation, so will XML be a catalyst for information programmability. XML makes it possible for web sites to share information, making the Web programmable.
Furthermore, XML is an industry standard, driven and approved by the W3C, the internationally-recognized standards body for Internet technologies.
At present, it’s easy for you to type in a URL and read the information presented on any web page you want. But it’s very difficult to get any one web site to interact with another, and even harder to do so in a scaleable and robust manner.
Thus, XML is ushering in the era of Web Services. In this era, web sites evolve into web services, their contents available not only to human eyes, but to Internet-based software, too.
In the near future, you will not only be able to browse the web, but program it, too. We want to make this possible not only for geeks like me, but for non-geeky users, in the way Visual Basic has enabled millions of developers to write applications for Windows.
Key success factors:
Simplicity
Standards

4. Forthcoming Architecture
The Inter/Intra/Extranet (PTP)
Message Bus on any Protocol
Conversation
Web
Service
Client
Subscribe
Web
Service
Msg
Stores
Data
Stores
Publish
Data
Stores
Web
Service

5. Third Generation Architecture: Program the Web
User
Web Site:
Applications
Page
HTML
Data
Object
XML
COM
Web Site:
Applications
Devices
The question becomes, where are we going from here?
what is the next generation of the Web going to look like?
At Microsoft, we think there are three key elements to this next generation:
the explosion of the Web connecting not just PCs, but “everything”. Handheld devices, cell phone, great increases in bandwidth, wireless technology: all of these trends fit in here.
The web becomes an applications integration architecture. So that you’ll see traffic not just between Web sites and end users, using HTML, but now traffic between corporate Web sites. In other words, Web servers directly exchanging information without the intermediation of HTML or browsers. XML is key here.
With all of these connected devices, and the increased value that comes from intelligent exchange of information, you start to see a transition away from software being a package to be installed and then run from a PC, and towards online services.

6. Windows DNA - The Guiding Architecture Windows DNA is Distributed Computing
Common object model on all tiers
Language neutral
“Auto-everything” - services for scalable, reliable, interoperable, distributed applications
Tools available today
This is DNA – Windows Distributed InterNet Architecture .
While some dismiss this as a combination of marketing and architecture – “marchitecture” – DNA offers real value as a roadmap for how to design, build, run, and manage distributed applications, taking advantage of the key capabilities of the Windows platform.
By now, this 3-tiered model should be familiar – this is the modern architecture that most applications strive for. The secret is: the idea of a 3-tiered architecture isn’t very new at all. In fact, transactional systems on the mainframe have been coded this way since the beginning – with presentation logic (3270 screens) separated from application logic (CICS transactions), which is separate from data (DB2 or ISAM). What we’re doing here is enabling this powerful, scalable, multi-tiered architecture with the high-productivity platform of windows, with all the support for rapid development and rich user interfaces you have come to expect from the windows platform.
Within DNA, all of our key strategic products play an important role.
Visual Studio – the tool suite for developing these distributed apps.
Windows - (Workstation/Professional) the platform for the “rich client” on the presentation tier.
Windows Server – the platform supporting the application or business logic, and the data logic.
Windows CE – a lightweight client front end.
Internet Explorer – the web browser as a presentation front-end into rich business applications
SQL Server – for structured back end data, OLAP or OLTP
Exchange – a distinct back-end data store for semi-structured data; Microsoft’s collaboration and and messaging backbone.
But while this list of products focuses on Microsoft offerings, we should be clear that Windows DNA does not preclude the use of non-Microsoft products. In fact, with Windows DNA, Microsoft is placing a new emphasis on interoperability and integration with existing IT investments that customers have made – whether they are on the browser side, the mid-tier, or back-end databases. [You can mention specific competitors products here if it makes sense for the opportunity or account.]
Windows DNA will thus serve as the basis for Microsoft’s push into the next generation of Web-enabled applications…. (leads into next slide).

7. Microsoft’s Application Platform Value Proposition
A single, rich, fully capable platform for new enterprise applications, with the best build and buy flexibility
Ease and Low-cost of Development, via tools tightly integrated with runtime environment
Plug into and re-use existing customer investments on desktop, back-ends, development languages and skills
Industry leading price/performance
There’s a lot behind the 4 bullets on this slide. Let’s take them one at a time:
The rich application platform. Microsoft provides a single, highly capable application platform to support all of the enterprise systems you may build – e-commerce, line-of-business, knowledge-management, or otherwise; employing any computing model: RPC; Messaging; Distributed Objects; even Publish/Subscribe. Microsoft’s platform supports all of these models, and is high-performance, scalable, reliable, and manageable. No one else offers this comprehensive package. No one. Database vendors have a database-centric view of the enterprise. Tools vendors have no runtime. Smaller middleware vendors can aspire to address only a small piece of any solution. Most enterprises have a hodgepodge of middleware, with large areas of overlap between them. Microsoft puts it all in the platform. Furthermore, it’s integrated for you. You don’t have to tie it all together, because we’ve done this already.
On the development side – we strive to make it easy for developers to be productive in their language of choice. VB – the most popular development tool in the world, with X million users. Visual-C++ for high-performance. Java. And in the future, you will see other languages. We will support them all.
Existing investments include: Mainframe - data and transactions; existing distributed databases; systems; workgroup collaboration systems; desktops. The secret to this integration is COM – the component object model that ties everything together. For example – connect your line-of-business app to your system, via COM. Connect to your IMS system via COM. Connect your e-commerce site to your existing Lotus Notes deployment – via (yes!) COM !
And finally, the best price/performance on the planet, and getting better! The top 33 TPC benchmark results, in price/performance, are all on Microsoft Windows NT. Not Unix. Not Linux. NT.
So to summarize, these are our guiding principles as we work to enable our customers to build the next generation Web.
________________________________
Rude Q&A:
if you have a participatory audience you may hear questions or objections on this.
Q1. You say Microsoft has the most comprehensive offering for an application platform. What about IBM?
A: IBM has the most credible offering, next to Microsoft’s. But IBM’s is not nearly as tightly integrated. IBM has built its offering via acquisition, and as a result, now markets multiple competing products in many spaces. For example, across the 7 or so IBM application servers, there are 7 distinct object models, and poor integration between them. IBM has no common directory strategy. IBM’s product set is showing evidence of its lack of common ancestry.
Q2. Price/performance is good, but if you can’t scale up, it doesn’t help me!
At this date, the best TPC-C number for an all-microsoft application platform is just over 40,000 tpcC (this is for an 8-way Compaq Proliant server). On the other hand, the best number for a Unix system is about 115 tpcC (for a 64-way Sun). So clearly, for a single-machine configuration, Microsoft does not scale as high as Unix. However: #1, this may be irrelevant, and #2: this is changing. First, many enterprises and mission-critical systems are built from a set of lesser machines, rather than from a single large server. For example, Dell has a large number of servers supporting it’s high-volume e-commerce web site ($1b in revenue for July 99), but only a very few are top-end Dell servers. Most of them are 2-way machines. In Dell’s case, the maximum TPC-C number is irrelevant. Secondly, PC server vendors are investing in more exotic hardware, and this year will introduce 8-way servers based on Intel’s Profusion. These servers will be specifically tuned for Windows NT and Windows And in the near future, Intel’s IA-64 chip will support great advances in raw performance for Windows 2000 Server. The trend over the past 18 months has been a very quick closing of the performance gap between NT and Unix, as measured by TPC benchmark results. And we expect that trend will continue over the next 18 months.

8. The Target Today, But, The Internet Factor.
It’s Easy to Build Robust Applications for PC’s
PC-based Department-sized distributed applications are near ubiquitous
But, The Internet Factor.
Apps must be 24x7 – software as a service
More Reliable, More Scalable, More Secure
New apps developed and deployed as quickly as possible
Plug into all other corporate IT assets
ROI – considering full life-cycle: $$ for development, runtime, management

9. Windows DNA 2000
Next generation of building blocks for Windows DNA applications
Windows 2000 is the Cornerstone
Rock solid, high performance platform
Integrates core Windows DNA Application Services
“Friction-free” deployment and management
Set of new and enhanced services
Richer Web applications platform
Improved integration and interoperability
E-commerce is “built-in”
Exploit Windows 2000
All expected to ship by mid 2000

10. Windows DNA Presentation services
Rich client
Components
DHTML
HTML
Scripting
Win32
Thin client

11. Windows DNA Business logic
Windows NT as an application server includes best of breed services
Web
Transaction
Queuing
Security
Integrated
Write business logic as COM components
Object-oriented, 3-tier development
Build great services into Windows
Transactions
Load balancing
Component management
Support all languages
Simplified APIs for developers
Offline client support is critical
IIS
MSMQ
MTS

12. Windows DNA Data services
Simplified programmatic access
Universal data provider
Mainframe
Application services
Directory
Presentation services
RDBMS
Universal Data Access provides high-performance access to a variety of information sources, including relational and non-relational, and an easy to use programming interface that is tool and language independent.
Universal Data Access does not require expensive and time-consuming movement of data into a single data store, nor does it require commitment to a single vendor’s products. Universal Data Access is based on open industry specifications with broad industry support, and works with all major established database platforms. Universal Data Access is an evolutionary step from today’s standard interfaces, including ODBC, RDO, and DAO; and extends the functionality of these well known and well tested technologies.
The Microsoft Data Access Components enable Universal Data Access. These components include ActiveX Data Objects (ADO), Remote Data Service, (RDS, formerly known as Advanced Database Connector or ADC), OLE DB, and Open Database Connectivity (ODBC).
and
messaging
ADO
File system
OLE DB
Distributed transactions
and query processing across
multiple data stores

13. Windows DNA Interoperability services
Bi-directional application, data and network interop with mainframes, AS/400, UNIX and other platforms
Extends COM/COM+ to CICS, IMS, terminal oriented apps, Unisys, etc.
Extends MSMQ to MQSeries
Extends ODBC/OLEDB to DB2, Sybase, Oracle, VSAM
Delivers heterogeneous bi-directional data replication
Built-in extensibility via SDK
COM-XML-MSMQ
Application Integration
Data Integration
ADO-OLEDB-ODBC
Network Integration
TCP/IP and SNA
Std. LAN Protocols
DRDA - RLIO
XA, TDS, CLI and DB LIB
APPC, CLI-C, DPL
LU0, LU2 and MQSeries
OS/390, OS/400, UNIX
VSAM, DB2, Oracle, Sybase
CICS, IMS, MQSeries, Terminal Apps

14. Windows DNA 2000 New or Enhanced: Application Services
Microsoft
“Babylon”
Server
Microsoft
Commerce
Server
New or Enhanced:
Application Services
Legacy Interoperability
E-commerce (B2C)
Data Access/Storage
Development Tools
“Developer Success”
+ E-commerce (B2B)
+ Deployment and Management
Microsoft
SQLServer
Microsoft
BizTalk
Server

15. Windows 2000 Windows DNA Application Services
“Built-in” integrated applications server for building distributed Web applications
IIS high performance web server
Active Server Pages
COM+ component services
Transactions
Message Queue and Queued Components
Role-based security
Network Load Balancing
High performance XML support

16. COM+ Key Features COM+ makes it easier to develop, deploy, and administer Enterprise Scale, Component-based Applications
New services
Queued components
Events
Dynamic Load Balancing
Object Pooling
CRM
Improved services
Transactions, servers, security, administration
Interception
Unify COM and MTS for single programming, admin model
Improved interoperability
XA, TIP, CRM
100% compatible with existing COM and MTS components
Same or better performance

17. COM+: Simple, Powerful Programming Model
CreateInstance …
OK: SetComplete
Err: SetAbort
IUnknown
Context
Client
Attributes
Server

18. COM+ for Serving Applications
Using COM+ Services:
You write a “single user” component as though it were the only user of resources
COM+ provides the rich service environment to make your component multi-user, multi-threaded and resource-pooled.
All you have to do is:
Use your favorite COM-compliant tool and add attributes
COM+ Server Process
Concurrency
Security
Services...
Server-side Application Logic
IFoo
Application
Client

19. COM+ Queued Components
Features:
Delivery of: component creation, method invocation, and life cycle management over MSMQ queues with transactions
Benefits:
Increase application availability and resilience
Decouple application elements
Retain component programming model
IRecorder
Client
Application
Component
Server
Application
Component
IFoo
Recorder
MSMQ
Player

20. COM+ Event Service Publish-and-Subscribe model Late-bound design
Subscription management moved out of app code
Event Admin
Unicast
ICustLogin
Sink1
Event Database
Multicast
ICustLogin
Sink2
Sink3
Sink4
Application Client
Event Class
Unbound
IEventXXX

21. COM+ Component Load Balancing
Dynamic load balancing engine, based on response time
Available via AppCenter
Not included in base OS
Application
Client
create LB
Activator
track
Response Time Engine
LB Service
Response Time Runtime
Server Group
Server 1
IBank
coclass Bank
[LB=Yes,]
IIBank
select server

22. COM+ Object Pooling For use when JIT doesn’t work Pooled Objects :
When objects are expensive to initialize
When objects consume expensive resources
Pooled Objects :
Initialized once at startup
Pooled after SetComplete
Activate and Deactivate can be used to control recycling
Pool size governed by Min and Max parameters

23. Visual Studio Truly Integrated suite of tools
Analyzer, Modeler, Package & Deployment, SourceSafe, Respository, Component Manager
The “Enterprise Workbench”
Allows you to Leverage component support where appropriate – client or server

24. SQL Server 7.0 Best database for Line of Business
Self-tuning, self-managing
Scalable from laptop to cluster
Over 2000 apps available today
Best database for Data Warehousing and Business Intelligence
Only DB w/ integrated OLAP & ETL
Office 2000 integration
Fastest time to market
Three times faster, 1/3 the cost
3x tpmC per CPU vs. Oracle8i
Best SAP performance – any platform

25. Microsoft Data Engine (MSDE)
SQL Server 7.0 data engine
Full function and fully compatible with SQL Server 7.0 – same code - without the admin tools
Mobile and shared solutions
Easiest migration path to SQL Server
“Free!”
Visual Studio 6.0 and Office 2000 Developer
Available since Spring ‘99

26. Host Integration Server
Version upgrade to SNA Server
Bi-directional network, data, and applications interoperability with mainframes, AS/400, UNIX, and others.
Bridge legacy data into XML
Requires no new code on the host
Available by mid 2000
OS/390, OS/400, UNIX
VSAM, DB2, Oracle, Sybase
CICS, IMS, MQSeries, Terminal Apps
Application Integration
APPC, CLI-C, DPL
LU0, LU2 and MQSeries
Data Integration
DRDA - RLIO
XA, TDS, CLI and DB LIB
Network Integration
TCP/IP and SNA
COM-XML-MSMQ
ADO-OLEDB-ODBC
Std. LAN Protocols

27. AppCenter Server High Availability, Multi-Server Deployment and Management Environment
Multiple Server
Web Farm
Key Features
Fault Tolerance
Dynamic Load Balancing
Simplified Management
Remote Management
App and Content Replication
Staging/Deployment
Integrated App Monitoring
Load Testing
Capacity Analysis
WMI enabled
Single
Server … …
Available by mid 2000

28. Agenda
DNA Explored
Site Server
XML & BizTalk Server
Web Services

29. Commerce Must Haves User identification, authentication and targeting
Catalog browsing
Order capture
Transacted Order Processing
Analysis
Back-End Integration

30. Site Server 3.0 Commerce Edition
Order capture, routing, management
Market-based pricing
Internet EDI
Extensible, open
Integrate existing systems
Account, profile management
Online advertising
Targeted promotions
Direct mail
Samples, wizards, tools
Engage
Transact
Engage
Transact
Analyze
Analyze
Order analysis
Usage and content analysis
Site iteration

31. Every Site Needs Membership
If your site has:
Registered and anonymous users:
Can users register or update their accounts online?
Can you track millions of anonymous (cookie ID) users?
Private or sensitive content:
Do you roll your own authentication?
Can you change permissions w/o rewriting scripts?
Premium or subscription areas:
Can users subscribe without calling customer service?
Can you easily run temporary promotions?
Targeted marketing or sales information:
How hard is it to author personalized pages?
Can you tune personalization w/o rewriting scripts?

32. Membership At The Core Of Site Server And Your Site
Commerce Streamlined Sales/Services
Personalization Individualized Delivery
Membership Customer Accounts and Site Security
Analysis Refined Experience
Advertising Targeted Message

33. Membership Functions
Authenticate users and authorize access to content and applications
Cookies, Basic, HTML forms, Certificates, DPA
Store and manage user accounts
Self-registration and delegated user admin
Protect confidential user information
Create personalized Web sites
Active user object and design time controls
Build online communities

34. Membership Web Solutions Personal And Secure
Web Site Areas
Public
Anon Customers
Cookie Auth
Explicit Profiling
Registered
Repeat Clients
Cookie Auth
+ Group ACLs
Explicit Profiling
Secured
Members Only
Basic, Forms, & Certificates
Explicit Profiling
+ Targeted Mail
Subscribed
Premium Services
Basic, Forms,
& Certificates
+ Group ACLs
Explicit Profiling
+ Targeted Mail
+ Push
Consistent User Tracking & Analysis

35. Agenda
DNA Explored
Site Server
XML & BizTalk Server
Web Services

36. XML – A Closer Look 15334, 29.00, 50023, 1, “Ricardo”, … <book>
<id>15534</id>
<price>29.00</price>
<author>Ricardo</author>
<title>XML and Me</title>
<grade.level>college</grade.level>
</book>

37. XML Structure HTML in less then a paragraph. <!--HTML Snippet-->
<h1>Invoice</h1>
<p>From: C. Brooks. </p>
<p>To: C. McCall </p>
<p> Date: 2/1/99 </p>
<p> Amount: $ </p>
<p> Tax: 12% </p>
<p> Total Due: $5.00 </p>

38. XML Structure XML in less then a paragraph. <!--XML Snippet-->
<Invoice>
<From>C. Brooks. </From>
<To>C. McCall </To>
<Date>2/1/99 </Date>
<Amount>$ </Amount>
<Tax>12% </Tax>
<Total>$5.00 </Total>
</Invoice>

39. A “Well-Formed” XML Document
Attribute
XML declaration
<?xml version="1.0"?>
<Order o_id="7845" o_date=" " o_cur="USD" c_id="JANTOY" >
<ShippingAddress sa_city="Erie" sa_state="PA" sa_pcode="19130">
<Line l_text="Jan's Toys" />
<Line l_text="1818 Market Street" />
<Line l_text="3rd Floor, Room 1219" />
</ShippingAddress>
<OrderDetails>
<Item p_id="325" p_name="Whirlygig" od_qty="5" od_unitp="15.50" />
<Item p_id="326" p_name="Zapper" od_qty="2" od_unitp="10.25" />
<Item p_id="327" p_name="Whirlygig" od_qty="5" od_unitp="15.50" />
</OrderDetails>
<Comments>
This order replaces order 7844 which was cancelled by the customer.
</Comments>
</Order>
Root element
Element
Empty element
Start-tag
Content
End-tag

40. Multiple Applications Into A Solution
Customers
Business Framework
Data (Schema)
Accounting
Interfaces
Website
Shipping
Design Pattern
R&D

41. Composable Services Supplier A SAP Planning ERP Supplier B XML
Supplier C
Siebel
Supplier B
JD Edwards
XML Message
XML
Purchase Orders Inventory
Capacity
Online Sales
Planning
ERP
XML
Online Store
Consumers

42. BizTalk Server BizTalk Server Description
A Microsoft Product Under Development for Business Process Integration Through the Reliable Exchange of Business Documents
Natively Uses BizTalk Schemas
Natively Supports XML Documents
Integrates with Existing Systems Via Specific Support For
X12 EDI
UN/Edifact EDI
Recordsets
Simple flat file delimited or positional documents
Many transports

43. BizTalk Server Vision
Business Process Integration Within and Between Companies
Planning
ERP
Online sales Web site
BizTalk
Documents
Supplier A
Supplier B
Supplier C

44. Doing BizTalk With Windows DNA
Single
MTS TX
Context
SQL
Server
LOB F I R E W A L
ADO
DCOM or
DCOM Connector
COM Business
Logic Components
HTTP
IIS
SMTP
Exchange
DOM
Wrapper
IE5/COM
HTTPS
CIPM
BTS
Windows NT, MMC, PKI, Cert Server, WLBS

45. BizTalk Document Structure
The complete BizTalk Message
BizTalk message
Standard MIME & XML Message Headers
Envelope
<biztalk_1>encloses BizTalk Message
BizTalk root
BizTalk header
message & document handling info
Routing information
<delivery> encloses to/from routing info
Document body
<body> contains BizTalk Document
Business document
BizTalk Document - the business data

46. Current BizTalk Architecture
Org A
Org B
Application
Transport
App
Adapter
Adapter
Adpt
Adpt
BizTalk Server
Handler
Handler
Handler
Handler
Transport

47. BizTalk™ Server
Business process integration within or across organizations over the Internet via XML documents
Part of the BizTalk initiative
BizTalk Server
BizTalk.org and the public Schema library
BizTalk Framework
Available by mid 2000

48. BizTalk Server Capabilities
Trading
Profiles
Duluth Mutual
West Coast Sales
POs
Invoice
SQL
Trading Partner Profile Management
Business Desk (Profiles and Agreements)
Application Integration
EDI interoperability, XML tools for mapping formats
Automated document interchange
Content based routing, Digital Certificates (PKI)
Rich Management and Analysis
SDK for extensibility, direct app integration

49. Agenda
DNA Explored
Site Server
XML & BizTalk Server
Web Services

50. 1st & 2nd Generation Web Apps
“Dynamic Pages”
Browser
File
Web Server DB
In-house
systems
File
Web Server
Browser
1-1 correspondence of page to file

51. 3rd Generation Web
In-house
systems
“The Firewall”
Web site
Accessing another site today = HTML “screen scraping” or “your architect calls my architect”
Tomorrow, external Web sites become building blocks using XML
Web Services
Megaservices
Web service
File DB
“Dynamic Pages”
Browser
Web Server

52. Examples of Web Services
Location Services
Maps, routing, nearby locations…
Shopping Services
Order tracking, supply chain, auctions, coupons…
Information Services
Headlines, weather, horoscopes, TV times…
Communication Services
, instant messages…

53. Some Web Service Scenarios
Search engine enables you to program it without a browser
Travel site enables you to compare against other travel sites
Web customer relationship management software extended to search online White Pages
Traffic monitoring site communicates with PIM to calculate how long it will take you between meetings

54. Combining Web Services
Authentication
Billing
Calendar
SOAP
White Pages
Mapping (Location)
Traffic
Alerting

55. What SOAP Is Designed to perform Web method invocations
OS, object model, language agnostic
HTTP + XML on the wire
Works over existing Internet infrastructure
OS, language, and object model agnostic interoperability

56. SOAP Message Structure
The complete SOAP Message
Standard HTTP and SOAP HTTP Headers
HTTP Headers
<Envelope> encloses payload
SOAP Envelope
SOAP Header
<Header> encloses headers
Headers
Individual headers
SOAP Body
<Body> contains SOAP Method Call
Method Call & Data
XML Encoded SOAP Method Call & Data

57. SOAP Message Types SOAP defines three kinds of messages:
Call
Response
Fault
Response and Fault are optional

58. SOAP Sample Call POST /StockQuote HTTP/1.1
Host:
Content-Type: text/xml
Content-Length: nnnn
SOAPMethodName: Some-Namespace-URI#GetLastTradePrice
<SOAP:Envelope xmlns:SOAP="urn:schemas-xmlsoap-org:soap.v1”>
<SOAP:Body>
<m:GetLastTradePrice
xmlns:m="Some-Namespace-URI”>
<symbol>DIS</symbol>
</m:GetLastTradePrice>
</SOAP:Body>
</SOAP:Envelope>

59. Security Builds on HTTP security Firewalls can filter easily
HTTPS
X.509 certificates
Firewalls can filter easily
Does not pass application code
Developers/IT choose which methods to expose explicitly
Type safety

60. SOAP and Standards Builds on SOAP Spec v1.0 to IETF W3C XML standards
IETF HTTP standard
SOAP Spec v1.0 to IETF

61. Summary
Windows DNA provides a comprehensive, integrated platform for building distributed Web apps
Windows DNA 2000 delivers the next wave of building blocks for the platform
Windows DNA is the fastest and easiest way to build high-value distributed Web-enabled apps