by Offir Bakshitz via Windows Live for Developers on 11/3/2010 10:32:46 PM
A few weeks ago we announced that Messenger Connect was out of beta and available worldwide. I wanted to take this opportunity to share some details about one of the features I worked on: the Messenger Connect Chat Control. This control allows people on your site to chat in real time. Any user can view the chat session. To participate, a user simply needs to sign-in with a Windows Live ID, that is, with a Hotmail or Messenger account.
The Chat Control currently comes in two color themes: light and dark. Here are a couple of snapshots.
The Chat Control adds value to your site in a number of ways. Here are just a few.
Users will spend more time on your site
You’ll acquire new users through the social networks of your existing users
It requires no resources from your site and yet it is scalable and easy to add
You’re in control
A user who browses a site with the Chat Control sees a live steam of messages.
The user is requested to sign in with a Windows Live ID in order to participate.
Once signed in, the user can post messages. Messages posted by the user’s friends are highlighted in light blue.
When the user applies the Friends filter—as indicated by the yellow arrow—the user sees only messages made by the user’s friends.
If the rate of message posting becomes high, the Messenger service arranges people into virtual subgroups so that they are not overwhelmed with messages. When this happens, the user is still guaranteed to see all messages made by friends.
As shown above in the sign-in screen, the user can select a check box to indicate the desire to share a link with friends. If the user selects that check box, information about the page will be posted to the user’s feed in Windows Live. If the user has connected a Windows Live account to a Facebook account, the information will also be posted to the user’s wall on Facebook.
In addition, the user can choose to invite friends to participate in the chat. Clicking on the Friends tab shows friends who are currently online.
Choosing a friend in the list and then clicking Invite starts a private IM conversation with the user’s friend.
The Chat Control wouldn’t be complete without some administrative capabilities. The owner of the application ID—that is, the user whose Live ID was used to register for the application ID—has additional rights. Once you sign in to the Chat Control with the Live ID of the application owner, you will have the addition functionality of blocking users and deleting any messages.
Once a user is blocked by the owner of the application, that user will not be able to publish content to any chat on the site.
And obviously, users can also delete their own messages.
Let’s get down to the details of what it takes to add the Chat Control to your page. Here is an example of a minimal page that has only the Chat Control in it.
Interesting lines to note here:
o Line 11—Your application ID.
o Line 15—Here you give a name for the topic of conversation. When you place more than one Chat Control with the same event-name attribute in your site, they all render the same conversation.
This page can be a static HTML page. No server code is needed. When the Messenger Connect loader is loaded by the browser, it runs client-side code that scans the page looking for HTML tags prefixed with wl. After that, some client-side code runs and adds HTML elements to those tags, and then the Chat Control is rendered.
You may register for an application ID by going to http://manage.dev.live.com.
· To learn more about the Messenger Connect Chat Control, go to the Chat Control reference of our Messenger Connect documentation.
· To learn about other features of Messenger Connect, visit the Windows Live Developer Center.
Original Post: Introducing the Messenger Connect Chat Control
The content of the postings is owned by the respective author. AzureFeeds is not responsible for the contents of the postings. This site is automatically generated and cannot be reviewed for abusive content. If you find abusive content on AzureFeeds, please contact us. Designated trademarks and brands are the property of their respective owners. All rights reserved.