Talk:Application programming interface
|
|
jayesh amarnani is working on API.
Wait a minute, SNMP isn't an API is it? is is a potocol. Don't know much about CORBA, but I wouldn't call DCOM an API. Robneild 15:53, 16 Feb 2004 (UTC)
The definition at the top of this document is too inclusive, with the result that protocols would be considered APIs. The common use of the term is for a collection of classes or functions. CORBA is many things (protocol, language mappings, type system...) and it happens to include an API as well - the ORB API. But most people would not call CORBA an API. At most, it is a language for expressing APIs. Yaronf 23:31, Feb 18, 2004 (UTC)
You definition of API's is way too inclusive. The API is the
programming language interface provided to users, in that programming language. This
is different than protocols, which usually represent the "wire" format of
the actual communication. This might be the may web interfaces, IIOP in CORBA, or
the conventions used in a socket call. Representing these in XML and ontologies
are the next evoloution of Protocols - but not of API's. I content that API's
are to be minimized as they create basically the next N squared problem in that
to get them implemented in every language, you have a very uphill battle, let
alone making changes. Protocols, on the other hand, can evolve and you let
the languages find their way to create the protocol. The reference to
ontologies would fit with the Protocols, but not with the API.s
"It is generally lawful to analyze API implementations in order to produce a compatible one" ummm. If the wine group looked at a Microsoft WIN32 implementation they would be in trouble. I thought they would steer clear of Microsoft's implementation. Guess it depends what is meant by analyze. I would have thought once you have a specification for the API that is all you need e.g. "int time = GetTime()". Robneild 14:44, 17 Oct 2004 (UTC)
API Category
I was thinking about creating Category:Application programming interface, creating a reposity for all the API's that exist in wikipedia, (DirectX, win32, opengl, etc)
Little bit of confusion...
This may sound stupid but what is the difference between an API and a library?
Framework,API,Library,Protocol
Dear All
I think it is gona be a big miss understanding here, as a
programmer in the first place and Systems Analyst, i can tell that we are talking about this Pyramid:
-----------Program-----------
-------------Libraries-------------
-------------------APIs-------------------
-----------------------Framework-----------------------
Operating System Layer--->Protocols---> Operating System
the programmers usually make their own libraries using calls to APIs which usually be a part of a particular framework which must be based in a particular operatin system, and the operating system uses a protocol to manage the communication with another operating system.
as an example, if we are talking about :
The Program------------------------------
Programmer Made Library to manage what ever tasks---- .NET APIs (System.Windows, System.Windows.Form...etc)
.NET Framework-----------------------------
WINDOWS XP------------------------------
Best Regards Hossam Abbas