Focus is on a walk through Web services, from ASMX to WSE to Indigo, and how Indigo will plug and play into Visual Studio.
Ari just came onstage wearing a heartrate monitor on his head. This should be interesting.
His hospital system, demonstrated inside whitehorse, shows the connection to a BEA Web service. The demo starts, tracing Air’s heartrate and brainwave activity! Then a call is made to the Web service, from within the client applicaiton.
Digging into the code, we look at app.config files, and based on the values, TCP or HTTP, endpionts are created to the services. The bindings are also defined, one each for TCP and HTTP. Indigo exposes the endpoints very naturally.
The gaps in the brainwave activity demonstrates the need for reliable messaging. Stop the client. Stop the server. Drag and drop one attribute (ReliabilityBinding) onto the class, to specify that each packet is received (a) once and only once, and (b) in order. One line of code! What about security? Mutual X509 certificate attributes. Restart server. Reliable messaging and security in two lines of code.
Indigo 1.0 will ship with a message tracing application. First few batches of messages are clear text. Scrolling down in the tracing utility, you see the cipher information and a blob of encrypted bytes. Very cool.
Alternate authentications, such as a fingerprint scan, can be plugged-in to extend Indigo’s security model.
All of these features in Indigo version 1.0. More information in Room #2008 today.