Steve Millet - What is Indigo?
- Posted: Apr 10, 2005 at 12:46 AM
- 32,632 Views
- 13 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Steve Millet is an architect on the Indigo team. What is Indigo? Millet says "Our next generation platform for doing Web services and messaging infrastructure."
Then Steve spends the next 43 minutes taking you through what Indigo was designed for, and gives you a demo of how it could be used in your own applications.
More information on Indigo is available on the Indigo Developer Center on MSDN. There's also an introduction to Indigo over on MSDN TV (given by Indigo architect Steven Swartz).
Sorry for the shaky camera, we handheld this one. Scoble left his tripod at home. Naughty naughty.
If you just want to see the demo, fast forward to 32:33.
Then Steve spends the next 43 minutes taking you through what Indigo was designed for, and gives you a demo of how it could be used in your own applications.
More information on Indigo is available on the Indigo Developer Center on MSDN. There's also an introduction to Indigo over on MSDN TV (given by Indigo architect Steven Swartz).
Sorry for the shaky camera, we handheld this one. Scoble left his tripod at home. Naughty naughty.
If you just want to see the demo, fast forward to 32:33.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
It may be the case that when references are passed over a remote transport that keeping track of objects and their lifetimes is "difficult", but DCOM did it, Corba does it and .NET remoting does it. To promote the Indigo version of events you are going to need a better story than "it's difficult". Since Indigo doesn't do some things that Remoting does then it isn't a complete replacement, which is fair enough as they never said it was, but we need to be clear that the ".NET remoting isn't going away" is not just because we need to support existing code, i.e. there is still a point to using remoting.
Any comments on that?
Molly
Ovidiu
Keep it up guys! great video
I am developing a web service that takes as it's only input param an object (just a structure, really). That way I can add new parameters to the service by adding properties to that object w/o breaking existing clients.
Am I violating this loosely coupled rule?
I think it is OK, as long as when you add new members to the structure, it still has meaning if older clients are not supplying those values. So if you add a string member, the older client will essentially be passing null for that value (since it is not present) and you have to expect and handle that gracefully.
Indigo is just a messaging platform that allows applications to communicate together. Does it sound kind of like Web Services? Well, Indigo will make it easier to enable communication between applications whether they're on the same computer or on different computers across the internet.
With respect to your question about passing an object (just a structure, really), this does not violate the loosely coupled rule. Passing data "by value" is the primary goal. Keeping references to objects across computing boundaries creates object lifetime issues (aka ref-counting) when running in a distributed environment.
But you bring up a good issue. Versioning is still something one must think about in a loosely coupled world. If I version my Contract, can it be backward compatible with clients assuming the previous version? For ServiceContracts an additive approach will work. For operation parameters (aka messages), Indigo provides versioning support by utilizing the DataContract feature.
You can learn more about Indigo and download the March CTP (Customer Technology Preview) on MSDN at:
http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx
Hey Scobleizer,
how long will it take you media GURUS to finally split up an interview like this one into
- a portrait picture (on the Web)
- a, guesstimate, 10MB audio file 64Kb/sec
- and a, say, 20MB video for the five minute demo
=30MB!!!
INSTEAD OF A 130MB+ download?!!!
I appreciate your work for the community, but the approach is really amateurish!
THANKS
G
I realize that this is most likely defined as part of the endpoint's binding configuration, but is most of that communication xml based or object serialization based?
I can see if you are communicating from .net to java you would need to use xml, but what about .net to .net? What is the "preferred" communication type?
If xml based, what about performance versus direct serialized object communication? What did the demo use?
Any info appreciated!
Mark
Remove this comment
Remove this thread
close