Re: API or standard DLL?
- From: "Fred Kleinschmidt" <fred.l.kleinmschmidt@xxxxxxxxxx>
- Date: Tue, 24 Jul 2007 18:20:45 GMT
<louw.elbie@xxxxxxxxx> wrote in message
news:1185258062.689196.225340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there
I got a project where a client wants a API written to access external
product provider databases and return results as a recordset.
What is the difference between an API and standard DLL? As I
understand, API doesn't rely on any other
software than e.g. Windows APIs to perform a task?
Should one write the API in C++ or will VB.NET or C# work? If so,
will the API will depend on the dotNet framework to be loaded?
I think you have a mistaken idea of what an API is.
API stands for "Application Programming Interface" ; it is the
DESCRIPTION of things like the calling sequence of functions,
the available variables, structs, classes, etc., and how a programmer
should use those entities.
One can write an API without ever writting a single line of code.
--
Fred L. Kleinschmidt
Boeing Associate Technical Fellow
Aero Stability and Controls Computing
.
- References:
- API or standard DLL?
- From: louw . elbie
- API or standard DLL?
- Prev by Date: any suggestions about the book "Introduction To Distributed Algorithms" by Gerard Tel?
- Next by Date: Re: API or standard DLL?
- Previous by thread: API or standard DLL?
- Next by thread: Re: API or standard DLL?
- Index(es):
Relevant Pages
|
