This must be my Mac day. An interesting blog posting on Microsoft's alignment challenges between all the different real-time communication clients and various protocols it needs to support.
What I would like to see is a Communicator client for Mac rather than improving Messenger. Or even a Communicator Web Access for the Mac.
By now, some of you have heard the news. Today we launched Messenger for Mac 6.0, our first Universal application! It includes some exciting things, like federation with Yahoo, the ability to show “what I’m listening to” on my iTunes and a spell checker (yea!) as well as features that have been long standing requests like support for animated and custom emoticons. However, I know a number of you are bound to ask: “Where is A/V in Messenger for Mac!?!”
I said in my first blog entry that I’d try to shed light on how feature decisions get made, give you some examples, and address why A/V isn’t in this release.
The short version: we are working on it.
Right now, Windows Live Messenger (WLM) and Live Communications Server (LCS), are not quite in sync on their audio and video technologies. But, they are on a path to join up and move to a shared protocol in upcoming releases. Rather than write two sets of code only to have to throw one away in the coming months, we’re writing that common protocol for the Mac, and as we all converge we’ll have A/V in Messenger for Mac*.