Simple understanding of API development

xiaoxiao2021-03-06  68

Simple understanding of API development

LU_YI_MING (_AT_) sina.com 2004.11.5

First, Windows User

Microsoft has upgraded a number of windows's sections (as seen in Longhorn), then only the CLR class library API is provided, and Intel will increase the CPU's speed after several times, we can only write a hosted application.

C language can only be used to write the underlying drive, C can only be used to write CLR, forget com bar, IL, IL, X86 compilation completely exits the programmer's vision, IL is derived from various new languages ​​... IE Start support IL (more than ASP support IL is too horrible), the application on the Internet explosives (not now DHTML JavaScript or ActiveX), N now applications will start from IE in the IE (every day is the latest Edition, no virus, fix the bug in time, Microsoft simply puts IE as a desktop ...

Start thinking: When the hosted application is mainstream, and the Internet transmission speed reaches the hard disk access speed, it is meaningless to install the application locally. When the Internet private data storage security is quite in local storage, it is meaningless to save a personal file locally. The local file system will be forgotten by people, as long as there is a Windows. Microsoft starts designing IL CPU, Intel low three four-way Microsoft application for this CPU design license.

Second, the Windows server side

C / C still has to be retained, those server-side platform programs (ASP, databases) with high running efficiency are written with IL, and there may be problems in the CLR, so the basic C / C language API will remain.

Applications above the server-side platform are also their own languages, and the database is SQL, JVM with Java, ASP with IL.

Third, the response of open source

Open source community also develops IL virtual machines, running on Linux, BSD, Hurd, and Firefox; can also embed Apache, just like the road of Java.

In the library of open source IL virtual machines, About the API in memory, process, equipment, files, users, networks, etc., can encapsulate the API of the operating system such as Linux, and the API of windows, messages, drawings, etc. can be packaged. XWindow's API is implemented; the rest is similar.

If Microsoft does implement a better and stronger API, the open source community will also follow the upgrade API.

For open source communities, it is only a new project for IL hosted, all projects will continue, and existing APIs will continue to support. The market for the market will continue to continue. After the IL virtual machine in the open source community, Sun's Java / JVM also felt huge pressure.

Fourth, API development restriction

Memory API: Although hosting code manages memory, it is only the call to the operating system memory API. The development of memory API is limited to the upgrade of CPU / MMU or operating system.

Process API: Hosted Application is scheduled as a normal process. The development of the process API is limited by the upgrade of the operating system.

Equipment API: The standard interface is limited to the upgrade of the operating system. Special calls are limited by the development of equipment. Managed is just the package of both.

File API: Upgraded by the file system. Host API is just a package of file system C API (or system call).

User API: Upgraded by the operating system user management. The hosting API is also only packaged.

Network API: A limited to the development of network protocols and applications. The upgrade of IPv4 to IPv6 is not directly related to the hosting. Hosting applications may lead to the emergence of new senior agreements.

Graphics API: Hosting is a package, message, drawing, etc. API package, drawing API is limited to the upgrade of graphics cards, which has made great progress in this year.

Component API: Component's search, communication will change significantly because of hosted applications.

It is integrated that the basic API is still developing on their respective tracks. The hosting can be regarded as another type of call of the basic API, and the advantage is to enhance safety control and prepare for code flow.

V. Changes and competition from API development

Traditional personal application

Microsoft Although the new API only provides the IL class library, it will not immediately stop the support of the old API, so the application developer can migrate to IL when appropriate. The core algorithm of the application will not have much change, but the user interface may need to upgrade as soon as possible, the problems brought about the cost, risk and competition, and the balance between the benefits. Open source communities will quickly imitate on their own platform.

2. Server application

There is little change, whether it is technology or competition, existing J2EE / .NET mode can continue, even if the IL virtual machine in the open source community is really mature, it is only a similar choice.

3. New Application Brought by Managed Code Flow

High-risk and big opportunities coexist, and now you can't see it.

4. Microsoft, open source community and IBM

The hosting will make Microsoft a few years of leading time. Open source communities are still booming, and they are constantly chasing the footsteps of Microsoft. IBM will tell the final user's open source software with a businessman's practice, especially on its own server, and provide reliable and thoughtful service guarantee.

6.

Linux platform technology structure

WINDOW platform technology structure

转载请注明原文地址:https://www.9cbs.com/read-93995.html

New Post(0)