About: Stub (distributed computing) is a research topic. Over the lifetime, 635 publications have been published within this topic receiving 9459 citations.
TL;DR: Overall it is found that the analytic models provide good descriptions, generally modeling the various distributions as well as empirical models and in some cases better.
Abstract: We analyze 2.5 million TCP connections that occurred during 14 wide-area traffic traces. The traces were gathered at five “stub” networks and two internetwork gateways, providing a diverse look at wide-area traffic. We derive analytic models describing the random variables associated with telnet, nntp, smtp, and ftp connections, and present a methodology for comparing the effectiveness of the analytic models with empirical models such as tcplib [DJ91]. Overall we find that the analytic models provide good descriptions, generally modeling the various distributions as well as empirical models and in some cases better.
TL;DR: In this paper, a first air interface is used to initiate communication between a wireless client and a remote server at least partially using a first wireless access point, and the server sends the wireless client a stub of a distributed object.
Abstract: Methods, apparatus, and business techniques are disclosed for use in distributed communication systems comprising a plurality of communication protocols. In one embodiment a first air interface is used to initiate communication between a wireless client and a remote server at least partially using a first wireless access point. The server sends the wireless client a stub of a distributed object. The stub is used to instantiate an object class. The object class defines an interface that the remote client can use to communicate with the remote server using an upper layer interface. The distributed object stub also provides an implementation of a software radio configuration for a set of lower protocol layers in a second air interface. The wireless client can thereby communicate with a second wireless access point using said second air interface protocol. Exemplary embodiments of the present invention are disclosed that focus on toll-tag and electronic-commerce related highway systems, distributed federated wireless access systems, and wide area wireless system capacity augmentation.
TL;DR: In this article, the authors propose a Domain Name Router (DNR) that uses domain names to route data sent to a destination on a network (e.g., a stub network).
Abstract: The present invention provides for a Domain Name Router (DNR) that uses domain names to route data sent to a destination on a network (e.g., a stub network). Each corporate entity or stub network can be assigned one or a small number of global addresses. Each of the hosts on the stub network can be assigned a global address. When a source entity sends data to a destination entity with a local address, the data is sent to the DNR using a global address. The source entity embeds the destination's domain name and its own domain name inside the data. The DNR extracts the destination's domain name from the data, translates that domain name to a local address and sends the data to the destination.
TL;DR: In this paper, a system and a method for implementing remote procedure calls in a distributed computer system (Figure 2) provide a base object class from which all distributed objects can be derived.
Abstract: A system and a method for implementing remote procedure calls in a distributed computer system (Figure 2) provide a base object class (Figures 1(1) and 1(2)) from which all distributed objects can be derived. A program extracting all classes derived from the base class provides an inheritance tree (Figure 3(a)) to allow down casting from a root class to a base class and to allow passing high level data structure between participants of a remote procedure call. An Unix script provides stub routines (Figures 7a and 7b) for implementing client-server model communicating processes.
TL;DR: In this article, the server process identifies an interface to pass to the client process and creates a stub object for receiving a request to invoke a function member of the interface and for invoking the requested function member upon receiving the request.
Abstract: A computer method and system for passing a pointer to an interface from a server process to a client process. In a preferred embodiment, the server process instantiates an object that has multiple interfaces. The server process identifies an interface to pass to the client process and creates a stub object for receiving a request to invoke a function member of the interface and for invoking the requested function member upon receiving the request. The server process then sends an identifier of the stub to the client process. When the client process receives the identifier of the stub, it instantiates a proxy object for receiving requests to invoke a function member of the interface and for sending the request to the identified stub. The client process can then invoke the function members of the interface by invoking function members of the proxy object. The proxy object sends a request to the identified stub. The identified stub then invokes the corresponding function member of the interface.