Abstract: Application information is sent from an ADSI server to an ADSI compatible device using TCP/IP. Application protocol information is encapsulated according to ADSI message layer and datalink layer protocol specifications to form a bit stream of application information. The bit stream of application information is passed to a socket interface of a TCP/IP protocol stack in the server to form a TCP/IP representation of the application information. The TCP/IP representation of the application information is sent from the ADSI server to the ADSI compatible device over a TCP/IP based network. The TCP/IP representation of the application information is received into a TCP/IP protocol stack in the ADSI compatible device. The bit stream of application information is retrieved from a socket interface of the TCP/IP protocol stack in the ADSI compatible device. The application protocol information is unencapsulated from the retrieved bit stream of application information.

Abstract: A development system for generating an automated server application program includes a server and a development tool. The server is responsive to a set of server control signals for providing a service to an expanded capability telephone via a telephone network, the service being in the form of signals that are exchanged with the expanded capability telephone. The development tool generates the set of server control signals, and operates by generating a set of graphical interfaces for displaying current service parameters to a developer, and receiving new values of the service parameters from the developer. A set of objects are provided in the development tool, each possessing predefined properties and exhibiting predefined behavior, whereby the set of objects defines the functionality of the development tool.

Abstract: A distributed-object software application is capable of recovering from a server crash. The recovery is transparent to the client objects because the client objects do not have to be re-started or re-loaded. Proxies on the client machine handle the details of communication over the network with server objects. An intelligent proxy detects a server crash when no response is received from the server object. The intelligent proxy then sends a name identifier of the server object to a locator. The locator looks up the name identifier and returns a remote reference to another running instance of the server object. If no other running instance exists, the locator loads the server object onto another server machine. The intelligent proxy uses the remote reference from the locator to establish a connection with the new server machine and a session with the new server object. The intelligent proxy stored the last state of the server object before the crash.

Abstract: A distributed client-server application is modified while running. The application is not stopped so that updating of objects is transparent. A meta server catalogs all object classes for both the server and the clients. Modifications are specified by a run-time update tool and converted to change commands. The meta server receives the change commands and updates the structure of an application database. Object class definitions are read from the meta server and modified by the meta server to access the new structure of the application database. The modified object-class definitions are written back to persistent storage for the meta server, and compiled and linked to form new object classes. An object adaptor receives a list of modified object classes from the meta server and notifies all server and client caches of the object classes on the list. The obselete objects are invalidated by the caches and new objects are created using the most up-to-date class definitions.