Notes from the general session given by Don Box and Doug Purdy today:
There is only one program and it is still being written.
Choice is an illusion. It's extremely difficult to change The Program. Redeploying the world is not an option. Change must happen incrementally, if at all. The four tenets of SO:
- Boundaries are explicit
- Services are autonomous
- Share schema & contract, not class
- Policy-based compatibility
Objective interpretation is an oxymoron. For any XML instance, there are any number of schemas that can describe it.
Good contracts make good neighbors. Defining explicit boundaries facilitates better interactions.
Innovate locally, interop globally. Innovations make our little neighborhood better, but for innovation, we must introduce as little new techonlogy as possible.
How much DOM does the The Program need? COM is necessary to keep our part of The Program running. Indigo will have first-class access to COM in the future.
How much Remoting does The Program need? Remoting is a CLR feature useful for cross appdomain scenarios. Remoting is great for certain scenarios. It's still evolving, improving.
How much ES does The Program need. ES is the easiest way to take advantage of DCOM for fast cross-machine access thanks to the investment in making DCOM fast and secure.
When in doubt, use ASMX. ASMX will be faster than remoting. We're trying to make ASMX and Remoting just as fast as DCOM.
How any WS-* does The Program need? Less.
How much WSE does The Program need? It gives us SSL's behavior in a transport neutral way via WS-Sec, WS-Trust, and WS-SecCon. If you need those today, WSE provides that part of The Program. Facilitates multi-hop, multi-transport scenarios.
Great presentation guys!
Posted
May 24 2004, 11:02 AM
by
Aaron Skonnard