Microsoft Will Release APIs To Satisfy Mandates

Opening access benefits developers; license fee on tap for protocols.

Microsoft's efforts to comply with last year's settlement of federal antitrust charges could be a boon to software developers. Last week, the software vendor said it will publish never-before-released application programming interfaces and communications protocols to satisfy the government's mandates.

The APIs relate to middleware that plaintiffs in the case say is too closely intertwined with the Windows operating system. Releasing the APIs may even the playing field for developers of rival Web-browsing, media-streaming, E-mail, and messaging applications, because computer makers and users will be able to deactivate Microsoft programs such as Internet Explorer and substitute other software in their place.


More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Some business developers say access to the APIs also will help them build richer applications that operate better in the Windows environment. "It's a big win for developers," says Tom Militello, president of the Software Developers Association of North Carolina and a developer for a large communications equipment and software vendor. Access to the messaging APIs may be particularly valuable as companies seek to build real-time collaboration apps for Windows that could communicate with software running on other platforms, he says.

Key Provisions

Giving developers access to critical APIs and disclosing server protocols is just the start of the settlement Microsoft reached with the Department of Justice last year.

  • Computer manufacturers must be free to install competing middleware (browsers, E-mail clients, etc.) without threat of market retaliation.

  • Microsoft must license its operating system to all PC makers on even terms for the next five years.

  • TA panel of three on-site, independent computer experts will monitor Microsoft's compliance.

  • The APIs will be in Service Pack 1 for Windows XP, expected to ship Aug. 28. They'll also be available free via Microsoft's Developer Network Web site. Microsoft, which still must win approval of the federal settlement from an appeals court, has identified 272 APIs used by Internet Explorer, Java Virtual Machine, Media Player, Messenger, and Outlook Express.

    Microsoft will charge a license fee for the 123 communications protocols that the Windows desktop operating system uses to communicate with servers. The protocols will be grouped into task-based bundles. For example, there will be a protocol group for creating file servers. "There's substantial intellectual property and valuable technology in these protocols," says Brad Smith, Microsoft's senior VP and general counsel. The company is withholding a Windows File Protection API and a remote procedure protocol. Smith says Windows' users security could be compromised if these fell into the wrong hands.

    Microsoft's moves could help the vendor fend off threats from the Linux open-source community, IDC analyst Dan Kusnetzky says. "Traditionally, it has been difficult for some developers to work with Microsoft because they have limited access to code. This could alter things."

    Microsoft last week also settled with the Federal Trade Commission, which charged that the vendor had falsely claimed that purchases made using its Passport Web service were more secure than typical E-commerce transactions and that Microsoft didn't employ "reasonable and appropriate measures" to protect users' personal data.

    Microsoft must enhance its Passport security systems and have them inspected by an independent professional every two years.


    Related Reading




    Currently we allow the following HTML tags in comments:

    Single tags

    These tags can be used alone and don't need an ending tag.

    <br> Defines a single line break

    <hr> Defines a horizontal line

    Matching tags

    These require an ending tag - e.g. <i>italic text</i>

    <a> Defines an anchor

    <b> Defines bold text

    <big> Defines big text

    <blockquote> Defines a long quotation

    <caption> Defines a table caption

    <cite> Defines a citation

    <code> Defines computer code text

    <em> Defines emphasized text

    <fieldset> Defines a border around elements in a form

    <h1> This is heading 1

    <h2> This is heading 2

    <h3> This is heading 3

    <h4> This is heading 4

    <h5> This is heading 5

    <h6> This is heading 6

    <i> Defines italic text

    <p> Defines a paragraph

    <pre> Defines preformatted text

    <q> Defines a short quotation

    <samp> Defines sample computer code text

    <small> Defines small text

    <span> Defines a section in a document

    <s> Defines strikethrough text

    <strike> Defines strikethrough text

    <strong> Defines strong text

    <sub> Defines subscripted text

    <sup> Defines superscripted text

    <u> Defines underlined text

    InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

    Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
    Subscribe to RSS

    Resource Links