| slovo | definícia |
application program
(wn) | application program
n 1: a program that gives a computer instructions that provide
the user with tools to accomplish a task; "he has tried
several different word processing applications" [syn:
application, application program, {applications
programme}] |
application program
(foldoc) | application program
app
application software
applications software
(Or "application", "app") A
complete, self-contained program that performs a specific
function directly for the user. This is in contrast to
system software such as the operating system kernel,
server processes, libraries which exists to support
application programs and utility programs.
Editors for various kinds of documents, spreadsheets, and
text formatters are common examples of applications. Network
applications include clients such as those for FTP,
electronic mail, telnet and WWW.
The term is used fairly loosely, for instance, some might say
that a client and server together form a distributed
application, others might argue that editors and compilers
were not applications but utility programs for building
applications.
One distinction between an application program and the
operating system is that applications always run in {user
mode} (or "non-privileged mode"), while operating systems and
related utilities may run in supervisor mode (or "privileged
mode").
The term may also be used to distinguish programs which
communicate via a graphical user interface from those which
are executed from the command line.
(2007-02-02)
|
| | podobné slovo | definícia |
application program interface
(foldoc) | Application Program Interface
API
Application Programming Interface
Applications Programming Interface
(API, or "application programming interface")
The interface (calling conventions) by which an {application
program} accesses operating system and other services. An
API is defined at source code level and provides a level of
abstraction between the application and the kernel (or
other privileged utilities) to ensure the portability of the
code.
An API can also provide an interface between a {high level
language} and lower level utilities and services which were
written without consideration for the calling conventions
supported by compiled languages. In this case, the API's main
task may be the translation of parameter lists from one format
to another and the interpretation of call-by-value and
call-by-reference arguments in one or both directions.
(1995-02-15)
|
application programming interface
(foldoc) | Application Program Interface
API
Application Programming Interface
Applications Programming Interface
(API, or "application programming interface")
The interface (calling conventions) by which an {application
program} accesses operating system and other services. An
API is defined at source code level and provides a level of
abstraction between the application and the kernel (or
other privileged utilities) to ensure the portability of the
code.
An API can also provide an interface between a {high level
language} and lower level utilities and services which were
written without consideration for the calling conventions
supported by compiled languages. In this case, the API's main
task may be the translation of parameter lists from one format
to another and the interpretation of call-by-value and
call-by-reference arguments in one or both directions.
(1995-02-15)
|
business application programming interface
(foldoc) | Business Application Programming Interface
BAPI
(BAPI) /bap'ee/ A set of
methods provided by an SAP business object.
Release 4.0 of SAP AG's R/3 system supports
object-oriented programming via an interface defined in
terms of objects and methods called BAPIs. For example if
a material object provides a function to check availability,
the corresponding SAP business object type "Material" might
provide a BAPI called "Material.CheckAvailability".
The definitions of SAP business objects and their BAPIs are
kept in an SAP business object repository. SAP provide
classes and libraries to enable a programming team to
build SAP applications that use business objects and BAPIs.
Supported environments include COM and Java.
The {Open BAPI Network
(http://sap.com/solutions/technology/bapis/index.htm)}.
gives background information and lists objects and BAPIs.
(2002-08-30)
|
calendar application programming interface
(foldoc) | Calendar Application Programming Interface
Calendar API
(CAPI, Calendar API) An API for calendar software.
Microsoft has defined a CAPI for their Schedule+
application.
(1995-01-11)
|
common isdn application programming interface
(foldoc) | Common ISDN Application Programming Interface
Common-ISDN-API
(CAPI, Common-ISDN-API) A programming interface
standard for an application program to communicate with an
ISDN card.
Work on CAPI began in 1989, focussing on the German ISDN
protocol, and was finished in 1990 by a CAPI working group
consisting of application providers, ISDN equipment
manufacturers, large customers, user groups and DBP Telekom,
resulting in COMMON-ISDN-API Version 1.1. Following
completion of the international protocol specification, almost
every telecommunication provider offers BRI and PRI with
protocols based on Q.931 / ETS 3009 102. Common-ISDN-API
Version 2.0 was developed to support all Q.931 protocols.
(http://capi.org/).
[Why not CIAPI?]
(1998-09-07)
|
generic security service application programming interface
(foldoc) | Generic Security Service Application Programming Interface
GSS-API
(GSS-API) An application level
interface (API) to system security services. It provides a
generic interface to services which may be provided by a
variety of different security mechanisms. Vanilla GSS-API
supports security contexts between two entities (known as
"principals").
GSS-API is a draft internet standard which is being developed
in the Common Authentication Technology Working Group
(cat-wg) of the Internet Engineering Task Force (IETF).
Initial specifications for GSS-API appeared in RFC 1508 and
RFC 1509. Subsequent revisions appeared in several draft
standards documents.
(http://dstc.qut.edu.au/~barton/work/project.html).
(1996-05-19)
|
internet server application programming interface
(foldoc) | Internet Server Application Programming Interface
ISAPI
(ISAPI) Microsoft's programming interface
between applications and their Internet Server. Active
Servers created with ISAPI extensions can be complete
in-process applications themselves, or can "connect" to other
services. ISAPI is used for the same sort of functions as
CGI but uses Microsoft Windows dynamic link libraries
(DLL) for greater efficiency. The server loads the DLL the
first time a request is received and the DLL then stays in
memory, ready to service other requests until the server
decides it is no longer needed. This minimises the overhead
associated with executing such applications many times.
An HTTP server can unload ISAPI application DLLs to free
memory or preload them to speed up the first access.
Applications can also be enhanced by ISAPI filters
(1997-01-06)
|
mail application programming interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
messaging application programming interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
microsoft mail application program interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
scheduling application programming interface
(foldoc) | Scheduling Application Programming Interface
Scheduling API
(SAPI, Scheduling API) An API aimed at software which aids
humans in arranging their (business) activities.
Microsoft has defined a SAPI for its Schedule+
application.
(1995-01-11)
|
speech application programming interface
(foldoc) | Speech Application Programming Interface
(SAPI) Microsoft's standard API
for speech synthesis and speech recognition in Windows 95.
The idea is to let developers try out and use various
low-level speech software from any number of verndors, while
retaining the same API.
Mike Rozak is the lead of the SAPI project at Microsoft.
Numerous major speech vendors have announced SAPI-support
plans. SRAPI, the competing speech recognition API by
Lotus/WordPerfect, is fast becoming obsolete.
(1996-03-04)
|
speech recognition application program interface
(foldoc) | Speech Recognition Application Program Interface
SRAPI
(SRAPI) Novell, Inc.'s high level API for
speech recognition which will be rolled out with
WordPerfect 7.0 and Perfect Office 7.0. SRAPI is in
competition with SAPI from Microsoft, a high level API
which currently addresses command and control (but not yet
dictation).
[Byte; March 1996; page 30; "Battle of the Dictaion APIs"].
(1996-03-12)
|
telephone application program interface
(foldoc) | Telephone Application Program Interface
(TAPI) Officially it's
Telephony Application Programming Interface.
(1995-11-27)
|
telephony application programming interface
(foldoc) | Telephony Application Programming Interface
TAPI
(TAPI, or "Telephone Application
Program Interface") A Windows 95 {Application Program
Interface} enabling hardware independent access to telephone
based communication. TAPI covers a rather wide area of
services from initialising the equipment (e.g. a modem) and
placing a call to voice mail or control of a remote
computer.
[Telephone or Telephony?]
(1995-12-05)
|
|