[omniORB] omniidl-generated file size
Renzo Tomaselli
renzo.tomaselli@tecnotp.it
Tue, 2 Feb 1999 17:31:48 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0016_01BE4ED1.E9840F70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi OmniORB developers,
setting up applications made up of many modules is becoming an issue =
as far as total size is concerned (at least on NT). Omniidl generated =
skeleton files are constituted out of three main parts:
1. helper stuff for values;
2. proxy methods;
3. skeleton methods.
Implementations need 1 and 3; clients 1 and 2. All the others only 1 =
(all things such as IDL type definitions, no interfaces). Now every =
module has to include all of them; this makes complex applications =
pretty heavy, particularly when they are almost colocated.
What about emitting the above parts on demand, according to a =
compilation parameter ? Or any other suggestion ?
Thanks,
Renzo Tomaselli =20
-------------------------------------------------------------------------=
--
TecnoTP s.n.c. Special Information System Design
Maso Pelauchi I38050 Ronchi Valsugana, Trento TN ITALY
Tel. +39 0461 773164 Fax. +39 0461 771514
e-mail: renzo.tomaselli@tecnotp.it =20
-------------------------------------------------------------------------=
--
------=_NextPart_000_0016_01BE4ED1.E9840F70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3007.2"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi OmniORB developers,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> setting up =
applications made=20
up of many modules is becoming an issue as far as total size is =
concerned (at=20
least on NT). Omniidl generated skeleton files are constituted out of =
three main=20
parts:</FONT></DIV>
<DIV><FONT size=3D2>1. helper stuff for values;</FONT></DIV>
<DIV><FONT size=3D2>2. proxy methods;</FONT></DIV>
<DIV><FONT size=3D2>3. skeleton methods.</FONT></DIV>
<DIV><FONT size=3D2>Implementations need 1 and 3; clients 1 and 2. All =
the others=20
only 1 (all things such as IDL type definitions, no interfaces). Now =
every=20
module has to include all of them; this makes complex applications =
pretty heavy,=20
particularly when they are almost colocated.</FONT></DIV>
<DIV><FONT size=3D2>What about emitting the above parts on demand, =
according to a=20
compilation parameter ? Or any other suggestion ?</FONT></DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT color=3D#000000=20
size=3D2> &nbs=
p;  =
; =
=20
Renzo Tomaselli =20
<BR>---------------------------------------------------------------------=
------<BR>TecnoTP=20
s.n.c. Special Information System Design<BR>Maso Pelauchi I38050 Ronchi=20
Valsugana, Trento TN ITALY<BR>Tel. +39 0461=20
773164 Fax. +39 0461 771514<BR>e-mail: <A=20
href=3D"mailto:renzo.tomaselli@tecnotp.it">renzo.tomaselli@tecnotp.it</A>=
=20
<BR>---------------------------------------------------------------------=
------</FONT></DIV></BODY></HTML>
------=_NextPart_000_0016_01BE4ED1.E9840F70--