Bloomer J., "Power Programming with RPC", O'Reilly & Associates, Inc., 1992.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the request, sending the subqueries to the communication modules of the I involved, maintaining the state of the query, receiving for the results, and composing the response to the user. Communication among I C servers is implemented through a message passing library based on ONC RPC [15]. Distributed object management approaches like CORBA [16] which provide a much higher level of abstraction, encapsulation, and flexibility through an interface language are investigated as the means of integrating Cnet with the health care network. However, CORBA introduces additional overhead ....

Bloomer, J. Power programming with RPC. O' Reilly & Ass.; 1992.

....to allow this form of fragmented access. A client interface fragment can then be used as a named reference and is responsible for maintaining reference validity and for any transparent or independent locality that the model may support. Fragmented objects are similar to concepts used in RPC [20, 22], CORBA [138] DCOM [27] and Java RMI [167] The fragmented object model di#ers from these in that it provides support for connective objects and group interfaces that enables multiple levels of fragmentation, while the other systems provide only one level of fragmentation: separating client ....

....other systems provide only one level of fragmentation: separating client interface fragments and the remaining service fragments. Fragmented objects also di#er in that they can provide multiple client interface fragments dependent on the client. A client interface fragment is often termed a stub [22, 138, 167] and can be viewed as a simple proxy of the server object within a client server communication. The stub has CHAPTER 1. INTRODUCTION 6 Stub Stub Client Stub Client Skel Server Reference Stub Skel Skel Server Stub Object Skeleton Object Figure 1: A stub skeleton style communication. ....

[Article contains additional citation context not shown here]

J. Bloomer. Power Programming with RPC. O'Reilly & Associates, Inc., 1991. BIBLIOGRAPHY 267

....scalability and rules out automatic policy consistency across application boundaries unless applications are located on the same host. 2 For example, calling subject identity can be obtained using methods IObjectContext: IsCallerInRole( and ISecurityProperty: GetCallerSID( 14 5.5. SESAME SECURITY SESAME (a Secure European System for Applications in a Multi vendor Environment) is a European project started in late 1980s, and funded in part by the European Commission under its RACE program [34] SESAME technology is not a middleware. Instead, it is an ....

J. Bloomer, Power Programming with RPC. Sebastopol, CA: O'Reilly & Associates, 1992.

....Header File . 107 vi List of Figures Figure 1.1: Client server model one or more client programs communicate over a network with a server which provides some resource. 3 Figure 1. 2: Remote procedure call communication [4]. 5 Figure 1.3: Structure of cable amplifier networks. Signals propagate along the forward path from the head end through high bandwidth trunk amplifiers, then through smaller networks of distribution amplifiers, before arriving at destination ....

....systems. Client calling procedure Client Stub network transport arguments results Server Stub network transport arguments Server called procedure request messages reply messages reply messages request messages Network Figure 1. 2: Remote procedure call communication [4]. results 6 Unlike socket connections, which are assigned to a specific port number, RPC uses a daemon called the portmapper which controls all RPC connections. To distinguish between servers, the portmapper uses program and version numbers. The program number must be unique to each server on a ....

[Article contains additional citation context not shown here]

J. Bloomer, "Power Programming with RPC", O'Reilly & Associates Inc., 1991.

....quality computation can be done. All grid generators and visualization components are parallelized. As a consequence, several rendering and grid generation tasks can be computed at the same time. The parallelization was done using an asynchronous remote procedure call as described in Bloomer [Blo92]. According to Brodlie et al. BCE92] the presented program falls into the category of turnkey visualization systems. From the basic structure it also differs from the data stream oriented systems like Explorer, as the computation of a processing step does not automatically evoke the ....

J. Bloomer. Power Programming with RPC. O'Reilly Associates, Inc., 1992.

....communication protection, and AC independently of the underlying communication layers. They are Kerberos [IETF 1993, Neuman 1994a] GAA API [Ryutov 2000a] and SESAME [Kaijser 1998, Parker 1995] Application developers deliver inter application communications by other means (e.g. ONC RPC [Bloomer 1992]) This enables the use and mix of any desired communication protocols and media. However, developers are overburdened with the efforts to integrate security with the underlying communication technology. 37 Another type is middleware technologies, such as CORBA [OMG 1996b] DCE [Gittler 1995] ....

J. Bloomer, Power Programming with RPC. O'Reilly & Associates, 1992.

....TAPR Transformation Machines. The implementation is not complete, but it is sufficient to allow us to validate the core algorithms and to create TAPR Transformation Machines sufficiently powerful to instantiate PSG transformation templates for two different communications infrastructures, Sun RPC [7, 69, 70] and PVM [27, 28] We call the implementation, Pydist, in keeping with the conventions of the Python programming language community 1 . Pydist is an implementation of TAPR applied to the problem domain we have been considering in detail: transforming sequential programs to distributed programs. ....

John Bloomer. Power Programming with RPC. O'Reilly & Associates, Sebastopol, CA, 1992. (cited on page 129)

....disciplines. Systems programmers have always developed concurrent and client server applications using the bare tools provided by the operating systems. Some of the environments have become standards, either officially or de facto (Unix System V IPC[3] MACH s C threads[4] Sun Microsystems RPC[5, 6], Open Software Foundation s DCE[7, 8] while others will soon be endorsed and thus widely available (POSIX threads[9] The purpose of this paper is precisely to examine the support available right at the operating system level to exploit the inherent parallelism of multiprocessor servers and ....

.... complex, real application programs[15] Modern operating systems already provide the foundations for network programming, supplying the tools and services necessary to develop Client Server applications[16] Most of these applications can be written using the Remote Procedure Call paradigm (RPC)[5, 6]. This is a high level protocol that allows a program to call a procedure on a remote machine in a style that resembles local invocation. That is, the details of packing the arguments into a message, sending the message, scheduling a process in the server, invoking the remote operation and ....

[Article contains additional citation context not shown here]

J. Bloomer, Power Programming with RPC, O'Rilley and Associates, 1992.

....but it can be found in [9] The set of parameters that describe the model elements are provided in Table 1. The ff Rel i factor indicates the fraction of the server relation i that is cached in every client disk manager. Both clients and servers spent time for processing the critical path of RPCs [21, 5] in their Network Proc: Modules(NPM ) Table 2 shows some additional parameters used in the models of this section. The net proc parameter accounts for the extra CPU penalties that take place at the NPM processing elements. DBMS Operational Aspects V alue page size 2KBytes srv cpu mips 41 MIPS ....

J. Bloomer. Power Programming with RPC. O'Reilly and Associates, Sebastopol, CA, 1992.

....of this method in detail. 3 Interactive Java client CGI server applications on the WWW The main characteristic of a client server application is that a part of the application (client) requests the execution of a job, while the other part of the application (server) executes this job [Bloomer 1992]. The basic idea is that we write the client program as a Java applet and we modify our computer vision program into a CGI program. This program works as a server program and performs all the computationally expensive operations. The execution of Java applet is not very fast, but since the client ....

Bloomer J (1992) Power programming with RPC. O'Reilly & Associates, Inc.

....and integrating changes and or bug fixes requires initiative on part of the user. This led us to consider the alternative of providing users with remote access to running implementations of the algorithmic software over the WWW. Remote execution of software is equivalent to a remote procedure call [Blo92], and the HTTP servers used on the WWW provide such a facility through what is referred to as the Common Gateway Interface [McC94] Using this facility, users can benefit from access to expert knowledge in the form of computational methods without having to deal with the problems of installing the ....

J. Bloomer. Power Programming with RPC. O'Reilly & Associates, Inc., Sebastopol, CA, 1992.

....Standard, is a standard used by the United States government; software using this standard cannot be exported. For a more thorough explanation of encryption standards, see [36] 4 A more complete discussion of secure Open Network Computing (ONC) RPC and ONC RPC authentication is contained in [5]. 5 A historical perspective on capability based architectures may be found in [16, 27, 54, 55] Work on capability based architectures was fairly short lived and is virtually non existent today [21, 23] 6 Text is the Unix term for machine code; the text segment is portion of an object file ....

J. Bloomer. Power Programming with RPC. O'Reilly & Associates, Inc., 1992.

....i;j uses a universal textual language, referred to as UniT ext, which is human readable, as the interface between compiler tools and their users. Hence, F i;j are of two kinds: InF i;j : UniT ext T oolInput and OutF i;j : T oolOutput UniT ext. This idea has been successfully tested by the RPC [3] and CORBA [28, 29, 30] Note that by integrating T ool i and T ool j and T ool i and T ool k we obtain an architecture where tools T ool j and T ool k can operate in parallel. The paper is structured as follows: Section 2 describes the SEL language and shows how can one extend the core language ....

....appnode app; struct urttab urt; struct urotab uro; where deftab, dectab, appnode, urttab, urotab are C language types implementing SEL data structures DefTab, DecTab, AppNode, UrtTab, UroTab. void TransImage1(struct image Sem[ merge(Sem[0] def, Sem[2] def) merge(Sem[0] def, Sem[3] def) merge(Sem[0] dec, Sem[2] dec) merge(Sem[0] dec, Sem[3] dec) Sem[0] app = struct appnode ) malloc(sizeof(struct appnode) Sem[0] label = string( ifthenelse ) insertchild(Sem[0] app, 0, Sem[1] app) insertchild(Sem[0] app, 1, Sem[2] app) insertchild(Sem[0] app, 2, ....

[Article contains additional citation context not shown here]

J. Bloomer. Power Programming with RPC. O'Reillly & Associates, Inc., 1991.

....issues also need to be dealt with for each buffer implementation: ONC RPC systems provide their own control and synchronization mechanism that provides a simple mechanism in which the client blocks until the server returns. More elaborate message style control mechanisms can be constructed [5] to enable parallel processing in the client and the server. Buffered Collection and Buffered Iterator Patterns August 31, 1995 10 . mmap based shared memory does not, by itself, provide any mechanism for synchronization, so some other mechanism, such as semaphores, must be selected. If the ....

....memory buffer via memcpy and updates the cursize . writeData( P.vertex info.vertex info len, sizeof(P.vertex info.vertex info len) writeData( P.vertex info.vertex info val, P. vertex info.vertex info len sizeof( vertex ) 11.0 Examples Distributed ICrules Batch RPC on ONC RPC [5] DCE Pipes [8] 12.0 See Also Remote Proxy pattern [3] 4] Iterator pattern [3] Buffered Collection and Buffered Iterator Patterns August 31, 1995 13 13.0 Acknowledgments The following individuals contributed to the development and refinement of this pattern: Douglas Schmidt ....

John Bloomer, "Power Programming with RPC," O'Reilly & Associates, 1992.

....The service interface information is concerned with the SO s interfaces. Because they are static information which are not changed during run time, they are set once at the time when the SO starts. ffl Type Version: An SO s interfaces format. The interfaces may be CORBA IDL [13] RPC IDL [3], or Application level protocol using message passing. It has also a version or a release number. For example, this attribute has a value, Orbix IDL 2.0 . ffl Directory: In a case when the interfaces need an external specification, as like IDL file, this attribute is used. It has a directory of ....

John Bloomer. Power Programming with RPC. O'Reilly & Associates, Inc., 1992.

....OOFF run in a distributed environment. Communications are effected through Remote Procedure Calls (RPCs) RPCs enable the client program to make remote calls as if they were local procedure calls. We are currently using ONC RPC developed by Sun Microsystems Open Network Computing (ONC) group [10]. ONC RPC is the foundation for most of the distributed system utilities used today. For RPC communication, client and server stubs are added to each client and server, respectively. A stub is a communication interface that implements the RPC protocol and specifies how messages are constructed and ....

Bloomer, J., Power Programming with RPC, O'Reilly and Associates, Inc., Sebastopol, CA, 1992.

....and integrating changes and or bug fixes requires initiative on part of the user. This led us to consider the alternative of providing users with remote access to running implementations of the algorithmic software over the WWW. Remote execution of software is equivalent to a remote procedure call [Blo92], and the HTTP servers used on the WWW provide such a facility through what is referred to as the Common Gateway Interface [McC94] Using this facility, users can benefit from access to expert knowledge in the form of computational methods without having to deal with the problems of installing the ....

J. Bloomer. Power Programming with RPC. O'Reilly & Associates, Inc., Sebastopol, CA, 1992.

No context found.

Bloomer J., "Power Programming with RPC", O'Reilly & Associates, Inc., 1992.

No context found.

Bloomer J., Power Programming with RPC, O'Reilly, 1992.

No context found.

Bloomer, J. (1992). Power Programming with RPC. O'Reilly & Associates, Inc.

No context found.

Bloomer, J., "Power Programming with RPC", O'Reilly & Associates, Sebastopol, 1992

No context found.

Bloomer, J. (1992) Power Programming with RPC, O'Reilly & Associates, Inc., Sebastopol, CA.

No context found.

John Bloomer. Power programming with RPC. O'Reilly & Associates, Inc., 981 Chestnut Street, Newton, MA 02164, USA, February 1992.

No context found.

Bloomer J. Power Programming with RPC, O'Reilly & Associates, Inc (1991).

No context found.

John Bloomer. Power Programming with RPC. O'Reilly & Associates, 1992.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC