G. T. Almes, `The impact of language and system on remote procedure call design', Proceedings of the Sixth International Conference on Distributed Computing, May 1986, pp. 414--421.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....flexibility afforded by DCG together allow us to offer XML or object system levels of plug and play communication without compromising performance. 5.1. 2 Marshalling and Unmarshalling Minimizing the costs of conversions to and from wire formats is a known problem in network com munication [6]. Traditional marshalling unmarshalling can be a significant overhead [32, 117] and tools like the Universal Stub Compiler (USC) 99] attempt to optimize marshalling with compile time solutions. Although optimization considerations similar to those addressed by USC apply in our case, the dynamic ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Proceedings of the 6th International Conference on Distributed Computing Systems (ICDCS), pages 414-421, May 13-19 1986.

....following subsections we describe the marshalling and unmarshalling of PBIO s messages and provide some details on the use of record format de scriptions. 3. 1 Marshalling and Unmarshalling Minimizing the costs of conversions to and from wire formats is a known prob lem in network communication [19]. Traditional marshaling unmarshalling can be a significant overhead [20, 21] and tools like the Universal Stub Compiler (USC) 22] attempt to optimize marshaling with compile time solutions. Al though optimization considerations similar to those addressed by USC apply in our case, the dynamic ....

G. T. Almes, "The impact of language and system on remote procedure call design," in Proceedings of the 6th International Conference on Distributed Computing Systems (ICDCS), pp. 414-421, May 13-19 1986.

....the following subsections we describe the marshalling and unmarshalling of PBIO s messages and provide some details on the use of record format descriptions. 3. 1 Marshalling and Unmarshalling Minimizing the costs of conversions to and from wire formats is a known problem in network communication [19]. Traditional marshaling unmarshalling can be a signi cant overhead [20, 21] and tools like the Universal Stub Compiler (USC) 22] attempt to optimize marshaling with compile time solutions. Although optimization considerations similar to those addressed by USC apply in our case, the dynamic form ....

G. T. Almes, \The impact of language and system on remote procedure call design," in Proceedings of the 6th International Conference on Distributed Computing Systems (ICDCS), pp. 414-421, May 13-19 1986.

.... byte order changes (byte swapping) movement of data from one offset to another, or even a change in the basic size of the data type (for example, from a 4 byte integer to an 8 byte integer) This conversion is another form of the marshaling problem that occurs widely in RPC implementations [1] and in network communication. Marshaling can be a significant overhead[7,27] and tools like USC[21] attempt to optimize marshaling with compile time solutions. Unfortunately, the dynamic form of the marshaling problem in ECho, where the layout and even the complete field contents of the incoming ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Sixth International Conference on Distributed Computing Systems, Boston, Mass., pages 414--421. IEEE, May 1986.

.... byte order changes (byte swapping) movement of data from one offset to another, or even a change in the basic size of the data type (for example, from a 4 byte integer to an 8 byte integer) This conversion is another form of the marshaling problem that occurs widely in RPC implementations[1] and in network communication. Marshaling can be a significant overhead[4, 18] and tools like the Universal Stub Compiler (USC) 14] attempt to optimize marshaling with compile4 time solutions. Although optimization considerations similar to those addressed by USC apply in our case, the dynamic ....

G. T. Almes. The impact of language and system on remote procedure call design. In Sixth International Conference on Distributed Computing Systems, Boston, Mass., pages 414-- 421. IEEE, May 1986.

.... byte order changes (byte swapping) movement of data from one offset to another, or even a change in the basic size of the data type (for example, from a 4 byte integer to an 8 byte integer) This conversion is another form of the marshaling problem that occurs widely in RPC implementations [1] and in network communication. That marshaling can be a significant overhead is also well known[4, 24] and tools such as USC[18] attempt to optimize marshaling with compile time solutions. Unfortunately, the dynamic form of the marshaling problem in PBIO, where the layout and even the complete ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Sixth International Conference on Distributed Computing Systems, Boston, Mass., pages 414--421. IEEE, May 1986.

.... byte order changes (byte swapping) movement of data from one offset to another, or even a change in the basic size of the data type (for example, from a 4 byte integer to an 8 byte integer) 6 This conversion is another form of the marshaling problem that occurs widely in RPC implementations[1] and in network communication. Marshaling can be a significant overhead[4, 16] and tools like USC[12] attempt to optimize marshaling with compile time solutions. Unfortunately, the dynamic form of the marshaling problem in PBIO, where the layout and even the complete field contents of the ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Sixth International Conference on Distributed Computing Systems, Boston, Mass., pages 414--421. IEEE, May 1986.

....sender s native format and isolating the complexity of managing heterogeneity in the receiver. On the receiving side, PBIO must convert the received data into the format required by the receiver. This conversion is another form of the marshaling problem that occurs widely in RPC implementations[1] and in network communication. That marshaling can be a significant overhead is also well known[2, 12] and tools such as USC[10] attempt to optimize marshaling with compile time solutions. Unfortunately, the dynamic form of the marshaling problem in PBIO rules out such static solutions. The ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Sixth International Conference on Distributed Computing Systems, Boston, Mass., pages 414--421. IEEE, May 1986.

....(a header file) 4.1 Communication The code generation for remote communication is similar to a traditional stub generation [Jones 1985] The SOS kernel communication primitive is modeled after the V system RPC. The code of the stubs generated by FOG is similar to the extension for Modula 2 by Almes [Almes 1986] for the V system. FOG interfaces to SOS via the class hierarchies described in section 2.4. In addition it reuses marshaling for all communication protocols, encapsulated by channel and message classes. For instance, for the declaration: multiChannel ch; void send (int calledObject, String s, ....

Guy T. Almes. The impact of language and system on remote procedure call design. In Proc. 6th Intl. Conf. on Distributed Computing Systems, pages 414--421, Cambridge, Mass. (USA), May 1986. IEEE.

....choice. First, there are two problems with at least once semantics. If a server crashes, the repeated attempts to contact the server (especially in the case of a frequently called server) run the risk of clogging the network with packets. Also, there is the problem of non idempotent procedures [1]. If a timeout should occur solely because of a delay in the network transmission, a non idempotent procedure could execute multiple times with incorrect results. This could create errors in the application. Exactly once semantics are impossible to guarantee in a networked environment, since ....

....the user of essential control that is necessary in remote procedure call environments. For this reason, we to require host specification by the user. The user must directly specify the host in the form of an argument to the remote procedure call. One improvement of this idea presented by Almes [1] is the allowance of an optional argument that indicates the host. If it is not included, it is assumed that the client wishes to contact any version of that procedure with matching types. This idea is a part of the future work for our package. The second part of binding is finding the server on ....

[Article contains additional citation context not shown here]

G. T. Almes. The impact of language and system on remote procedure call design. In Proceedings of the 6th International Conference on Distributed Computing Systems, pages 414--421. IEEE, May 1986.

No context found.

G. T. Almes, `The impact of language and system on remote procedure call design', Proceedings of the Sixth International Conference on Distributed Computing, May 1986, pp. 414--421.

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