Citation Context

...plication includes information about the stubs and the surrogate objects (e.g., using include files in the CORBA C++ mapping [COR95]). We don't build a new system with a new language, as e.g. Emerald =-=[JuLe88]-=-, but emphasize the reuse of existing systems. Similar to the network objects [BiN94] we primarily try to keep our system simple without discriminating its generality. The main difference between our ...

Citation Context

...ndent byte streams and vice versa. 1.2 Just-In-Time Stub Generation Generation of stub and surrogate code can be highly automated. The common approach, e.g. chosen in CORBA [COR95] or Network Objects =-=[BiN94]-=-, is to generate stub and surrogate (also called skeleton code) statically, in advance, previous to the compilation of the client code. We delay the generation as long as possible and generate the nee...

Citation Context

...er is to add support for distributed objects to the Oberon system [Rei92]. In particular, distributed objects should support the implementation of distributed models (in the sense of the MVC paradigm =-=[KrP88]-=-), i.e., they should support the adaptation of existing Oberon applications (ease the transition of existing MVC applications) to a distributed environment. To ease this transformation we proclaim aut...

Citation Context

...d allow us to distribute objects without making the corresponding source code public. The stub generation is platform independent. It only requires an Oberon compiler using the portable front-end OP2 =-=[Cre90]-=-. As an example let's look at the following type definition (Figure 6): TYPE MyPtr = POINTER TO MyPtrDesc; MyPtrDesc = RECORD i: INTEGER; PROCEDURE (obj: MyPtr) Method (VAR i: INTEGER; p: MyPtr) END; ...