Browse Prior Art Database

IDL Meta Data

IP.com Disclosure Number: IPCOM000123960D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 1 page(s) / 72K

Publishing Venue

IBM

Related People

Berman, ES: AUTHOR [+4]

Abstract

Today Distributed Computing Environment (DCE) users on any DCE platform can use the On-line Standard Interface (OSF) IDL compiler to read an Interface Definition Language (IDL) file and generate C client server stub files. These stub files work in conjunction with the DCE/RPC runtime to marshall and route application data appropriately between client and server applications.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

IDL Meta Data

   Today Distributed Computing Environment (DCE) users on any
DCE platform can use the On-line Standard Interface (OSF) IDL
compiler to read an Interface Definition Language (IDL) file and
generate C client server stub files.  These stub files work in
conjunction with the DCE/RPC runtime to marshall and route
application data appropriately between client and server
applications.

   The Interface Definition Language (IDL) definitions are
architected by OSF and implemented in a standardized manner across
heterogeneous systems.  The customer application sees interface data,
but "metadata" such as interface names, entry point names, versions,
etc., are unavailable during execution, particularly if control has
been moved to a common path.

   Generally, a DCE server registers each supported interfaces
with the DCE runtime.  As part of this registration, the routing of
entry points within that interface is also defined, using an entry
point vector.  When the server stub is invoked, it directly routes
the call to the desired destination routine.  Since there is
generally a one-to-one mapping between the interface name/operation
name and the destination route in the server, the destination routine
can infer this IDL information contextually during execution.

   However, the DCE Application Server routes control from
server stubs for all interfaces and operations to a common
processing routine.  If an exit routine is invoked from this common
routine which requires the IDL interface or operation name, to do
conditional processing, this information is unavailable.

   For IBM OS/390(TM) DCE R5 the idl compile...