Application Programming Interface for Windows

The Application Programming Interface for Windows (APIW) Standard is a specification of the Microsoft Windows 3.1 API drafted by Willows Software. It is the successor to previously proposed Public Windows Interface standard. It was created in an attempt to establish a vendor-neutral, platform-independent, open standard of the 16-bit Windows API not controlled by Microsoft.[1]

History

Solutions for heterogeneous environments

By the end of 1990, Windows 3.0 was the top-selling software. The various graphical Windows applications had already started to reduce training time and enhance productivity on personal computers. At the same time, various Unix and Unix-based operating systems dominated technical workstations and departmental servers. The idea of a consistent application environment across heterogeneous environments was compelling to both enterprise customers and software developers.

On May 5, 1993, Sun Microsystems announced Windows Application Binary Interface (WABI), a product to run Windows software on Unix, and the Public Windows Interface (PWI) initiative, an effort to standardize a subset of the popular 16-bit Windows APIs.[2] They proposed PWI to various companies and organizations including X/Open, IEEE and Unix International.[3] The previous day, Microsoft had announced SoftPC, a Windows to Unix product created by Insignia Solutions as part of a program where Microsoft licensed their Windows source code to select third parties, which in the following year became known as Windows Interface Source Environment (WISE). Later that month, Microsoft also announced Windows NT, a version of Windows designed to run on workstations and servers.[4]

ECMA gets involved

In February 1994, the PWI Specification Committee sent a draft specification to X/Open—who rejected it in March, after being threatened by Microsoft's assertion of intellectual property rights (IPR) over the Windows APIs[5]—and the European Computer Manufacturers' Association (ECMA). In September, now part of an ECMA delegation, they made an informational presentation about the project at the ISO SC22 plenary meeting in The Hague, Netherlands.[6] Their goal was to make it an ISO standard in order to force Microsoft to comply with it (in Windows) or risk not being able sell to European or Asian governments who can only buy ISO standards-compliant products.[7]

In April 1995, Willows Software, Inc. (formerly Multiport, Inc.[8][9]) a Saratoga, California-based Canopy-funded company, that had been working on Windows to Unix technologies (inherited from then defunct Hunter Systems, Inc.[10]) since early 1993, joined the ad hoc ECMA group. This group became Technical Committee 37 in August (about the time Windows 95 was released). Willows vowed to complete a full draft specification by the end of the year. In October, the draft specification was completed under the name Application Programming Interface for Windows (APIW). This was accepted as ECMA-234 in December and was put on the fast-track program to become an ISO standard.[6]

ISO delays the standard

Again, Microsoft claimed intellectual property over Windows APIs and ISO put the standard on hold pending proof of their claims. The delay lasted until November 1997, when, hearing no response from Microsoft, ISO announced they were pushing through with the standard.[11] However, there is no record of it ever being approved as an ISO standard.

gollark: The partition my bot's database is on apparently has 100GB free.
gollark: My thing stores all its data in a single SQLite3 database which is apparently 32KB.
gollark: The only thing I have which stores data associated with a particular user is the `++remind` command, and I feel like people shouldn't set reminders if they don't want their user ID stored with them.
gollark: For most you can probably get away with manually handling requests.
gollark: My bot technically doesn't have a "clear user data" command, but it only stores user data if you explicitly run a command which obviously stores user data, and nobody asked to have their data deleted yet.

See also
  • Willows Toolkit for UNIX
  • Willows RT for Embedded Systems
  • Novell Corsair
  • Caldera Network Desktop

References
  1. "Standard ECMA-234" (PDF). Ecma International. December 1995.
  2. "SunFLASH Vol 53: Sun Introduces Wabi - Allows MS-Windows Apps To Run Under UNIX". SunFlash (Newsletter). May 1993.
  3. Cheryl Gerber (May 10, 1993). "Sun unveils Windows for RISC plans". InfoWorld. InfoWorld Media Group, Inc.: 8.
  4. Bob Metcalfe (June 7, 1993). "Is OS cross-dressing too good to be true?". InfoWorld. InfoWorld Media Group, Inc.: 52.
  5. "X/OPEN NOT TO TAKE MANAGEMENT OF THE PUBLIC WINDOWS INITIATIVE". Computer Business Review. March 30, 1994. Missing or empty |url= (help)
  6. Rob Farnum (June 1996). "Applications Programming Interface for Windows: A Timely Standard". StandardView. 4 (2): 100–102. doi:10.1145/234999.235003.
  7. Martin LanMonica (December 18, 1995). "Group back Windows spec". InfoWorld. InfoWorld Media Group, Inc.: 16.
  8. "CORSAIR EFFORT TO BECOME INTERNET OPERATING SYSTEM". Computer Business Review. March 17, 1995. Missing or empty |url= (help)
  9. "Corsair Desktop mit Linux-Kern" [Corsair Desktop Linux kernel]. Computerwoche. June 30, 1995. Archived from the original on March 23, 2012.
  10. "HUNTER'S PERSONAL COMPUTER APPLICATIONS UNDER UNIX TECHNOLOGY RE-EMERGES AT MULTIPORT". Computer Business Review. July 8, 1993. Missing or empty |url= (help)
  11. Carl Cargill (December 1997). "Section 2. Sun and Standardization Wars". StandardView. 5 (4): 133–135. doi:10.1145/274348.274350.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.