# ILU Reference Manual

### (1)

We might forbid two consecutive hyphens or add other restrictions.

### (2)

We may change this.

### (3)

Same integer in all protocols? Yep -- for now.

### (4)

OMG IDL is defined in: The Common Object Request Broker: Architecture and Specification, OMG Document Number 91.12.1, Revision 1.1

### (5)

The program's front end is derived from the Interface Definition Language Compiler Front End from SunSoft, Inc. See the file ``src/stubbers/idl2isl/Sun-parser/docs/COPYRIGHT'` in the ILU distribution.

### (6)

The Common Object Request Broker: Architecture and Specification, revision 2.0, Draft July 1995

### (7)

This causes problems; the ISL names "FooBar" and "foo-bar" map to the same Common Lisp name. Something will have to change.

### (8)

See section The ILU Common Lisp Portable DEFSYSTEM Module, for a description of the `PDEFSYS` package.

### (9)

RPC: Remote Procedure Call Protocol Specification, Version 2; R. Srinivasan. IETF RFC 1831, August 1995.

### (10)

XDR: External Data Representation Standard; R. Srinivasan. IETF RFC 1832, August 1995.

### (11)

Courier: The Remote Procedure Call Protocol; Xerox Corporation, XNSS 038112, 1981

### (12)

Query: can requests be larger than the UDP packet size? [No] How then are they segmented? [They're not; replies aren't either] Note: This should probably be replaced by a reliable UDP protocol, in which each message is acknowledged by the receiver. This would allow use of asynchronous methods over UDP. Of course, ONC RPC would not cooperate.

### (13)

The current ILU GSS implementation only allows one name per GSS identity. This restriction will be lifted in the future.

### (14)

Currently, it does this by marshalling one language's representation into a data buffer, as if to transmit it to another address space, then hands this buffer to the other language's ILU support, which unmarshalls it into representations appropriate for that language. We plan to optimize this process in the future.