DOMC Session 5: Future of CGI
Question: Is CORBA/IIOP a better alternative to CGI?
who also led the subsequent discussion and compiled
the following summary. Andreas is Senior Research Scientist with the
To get the discussion started I made the statement "CGI sucks"
which I thought would be rather provocative. However, instead of causing
an outcry of the masses the statement made quite a few heads nodding.
They have been most likely the heads of people who have actually implemented
non-trivial CGI-based applications.
To structure the discussion I made suggested the following five issues:
Separation of interface and implementation
general agreement that separation of interface and implementation
is a good thing
Multiple programming languages
There are currently 15+ ORB products available. CGI camp claimed to have
the far larger base of installations.
Integration of legacy systems/applications through object wrapping
The discussion came to a first conclusion, namely that
The discussion than turned towards how to integrate the WWW and CORBA.
The following approaches have identified:
CGI is a valid technique for simple interfaces, e.g. to fetch a document
and run a specific filter over the document.
CORBA is a superior technique when is comes to more complex, operational
interfaces, e.g. a home-banking application.
modify HTTP server so that the can translate specific HTTP request,
in particular of the URL type "IOR:..." into calls on interoperable
object references (IOR).
make CORBA objects understand HTTP
IIOP as part of the WWW protocol suite which would enable invocations
on interoperable object references (IOR) directly from a WWW browser.
Discussion attendees, please feel free to comment on this subjective view
on the discussion.