|
News
Issue #2001 - 41
(October 2001)
(Updated Oct.
12, 2001)
INFRASTRUCTURE, PRODUCTS & SERVICES
New Windows Boost For Instant Messaging
Microsoft plans to include APIs for writing advanced instant-messaging apps in the upcoming Windows.Net Server, and it may build a separate "real-time collaboration server" to manage them.
Two APIs and a communications update to TCP/IP are scheduled to appear in beta 3 of Windows.Net Server, due in November. With them, IT departments and independent software developers could build apps that let workers send instant messages that are encrypted, securely hosted, and allow for more sophisticated types of file transfer than is available today in Microsoft environments, according to Microsoft execs.
A lack of encryption, authentication procedures, and management tools is causing some IT departments to curb use of instant messaging, says Aberdeen Group analyst Dana Gardner. Advanced messaging apps will be valuable to companies with mobile users and customers who need updates on the fly, Gardner says. "Instant messaging is a bright spot in a rather lackluster period in the business."
In addition to developing server-side support for more secure instant-messaging apps, Microsoft is developing a, what it calls, a real-time collaboration server that would let IT departments manage IM apps built with Windows Messenger. One Microsoft exec says the server would let IT managers log the exchange of messages, and control whether messages can traverse a company's firewall. Microsoft hasn't decided whether to include that software in Windows, or sell it as part of another product.
For more information: www.microsoft.com
Mobileinfo Comments and Advisory: Instant
messaging is an important application in both wireline and wireless
environments. Microsoft's support in the upcoming Windows .Net
server is welcome.
Note: This news release may contain
forward-looking statements. Readers should take appropriate caution in
developing plans utilizing these products, services and technology
architectures. All trademarks used in this summary are
the property of their respective owners.
|