RE: About the source library

["Didier PH Martin" <martind@xxxxxxxxxxxxx>]

Hi Avi,

<Comment>
Please leave the module interface out of Jade! I'd hate to be tied to yet
another technology...

Of course, module interfaces are there for a reason, so here's what I would
do to support them:
1. Write a Jade backend which forwards all calls to Your Favorite Module
Interface (YFMI).
2. Write a YFMI adapter which can connect to this backend, and presents a
FotBuilder interface.
3. When a new backend is written, it can either be added directly to Jade,
or to the YFMI adapter, or to Somebody Else's Favorite Module Interface.

jade -t rtf     # internal backend
jade -t lib:postscript    # shared library/dll backend
jade -t lib:corba:whatever   # corba-based backend 'whatever' using
forwarding backend 'corba'

There can be thousands upon thousands of colons on that line... :-)
</Comment>

<reply>
about 1. very interesting suggestion with low impact on the actual code.

If I understand you well, this backend could make the transition between
Jade and the components. For instance, having a Jade to XPCOM adapter, Jade
to a particular CORBA ORB (we cannot say for direct access to CORBA in
general except if the inter module interface is IIOP, but this out of
question for performance issues. This is why I say a particular CORBA ORB -
i.e. an adapter for each CORBA ORB or family of ORB having the same module
binary signature for the interfaces),Jade to DCOM, Jade to dll, jade to
shared libraries, etc...

I checked this week end and for XPCOM, DCOM and ILU CORBA this means a
single function indirection when the module is used in process as a dll or a
shared library. This would not impact the expression language performance
(still in jade) and just impact formatting object creation. However, if the
backend does some caching between the beginxxx and endxxxx calls, the impact
is even more reduced.

Avi, this is a good thread. Thanks for the suggestion.
</reply>

regards
Didier PH Martin
mailto:martind@xxxxxxxxxxxxx
http://www.netfolder.com



 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist