|
HailStorm
Introduction
In March of 2001, Microsoft sent ripples through the computer
world when it announced its first product from its .NET initiative called HailStorm. HailStorm are a set of developer tools for writing new
applications and bringing existing Microsoft products into the .NET world.
These products initially comprised 14 software services including MyAddress, an
electronic and geographic address for an identity; MyProfile, which includes a
name, nickname, special dates and pictures; MyContacts, an electronic address
book; MyLocation for pinpointing locations; MyNotifications, which will pass
along updates and other information; and MyInbox, which includes items such as
e-mail and voicemail.
Functionality
Hailstorm is based on Microsoft's .NET Passport
user-authentication system, which permits applications and services to cooperate
with one another for the user's benefit, as well as allowing users, groups and organizations to
share and collaborate real time information. This would provide consumers
and business customers access to their calendars, phone books and address lists through
a PC, a smart
phone, a PDA, or any other smart connected device. With HailStorm, one
would
not have to be the bridge between his or her different devices and applications when
storing data, HailStorm would do it automatically.
The premise behind Hailstorm was to create a service that was centered around the user, instead of around a specific device, application, service or network. Microsoft believes HailStorm would allow users control of their own data and information, protecting personal information and providing them with a new level of user friendliness and personalization, putting to rest the security issues presented by companies distributing user's private information. HailStorm accomplishes this by allowing the user to control his or her own information by letting the user determine with whom to share his or her information and under what terms. Any access, changes, and use of that data would require the explicit consent of the user.
Technical Aspects
"The HailStorm platform uses an open access model, which
means it can be used with any device, application, or services, regardless of
the underlying platform, operating system, object model, programming language or
network provider. All services in HailStorm are XML Web services, which
are based on the open industry standards of XML and Simple Object Access
Protocol (SOAP); no Microsoft runtime or tool is required to call them.
HailStorm's architecture defines identity, security, and data models that are
common to all services and ensures consistency of development and operation."
(Microsoft White Paper)
The benefit to the user is time saved and a reduction of entry errors as HailStorm eliminates the user from having to re-enter and redundantly store his
or her information. The developer benefits by not having to create a
unique system for these basic capabilities and time saved from the common
software maintenance issues. However, this time saving service does not come
without a cost. Microsoft is going to charge the user and developer a fee
for the use of HailStorm and other .NET services.
Response to
HailStorm
Since the announcement of HailStorm in March of 2001, its
reception was not well received by competitors, businesses targeted by Microsoft,
and special interest groups.
Competitors believed that Microsoft was trying to stifle competition and lock in
users into its .NET strategy, thus strengthening Microsoft's software market monopoly.
As for the business segment targeted by Microsoft, nine months of intense
efforts proved fruitless as the software giant was unable to find any business
willing to commit to their program. If two strikes against HailStorm were
not enough for Microsoft to change its strategy,
several consumer groups filed complaints with the Federal Trade Commission
alleging HailStorm and its related services violated federal consumer protection
laws. These less than happy responses to HailStorm, has forced Microsoft to
abandon its HailStorm platform.