Originating from a discussion during the MUG'99 meeting, it was intended to provide a depiction tool, i.e., a utility for delivering customized 2D depictions in a distributed manner. During development last summer, it evolved into a generic program object based compute server which is likely to be useful for many other purposes. This type of depiction server was implmented as adeptserver (adept = a depiction tool) and described at EMUG'99. As it turned out, an unfortunate choice of name...
Experience with development of special-purpose HTTP servers (e.g., daliserver, terravivo) suggested a completely different approach: casting the depiction server as a pure HTTP service. A pure HTTP depict server was implemented as imagine (image engine) It is likely that such a service will be more compatible with the future Daylight CGI system.
(+) ipcx/tdt-based -> efficient
(+) database-oriented-> scalable
(+) oopish toolkit interface
(+) extensible to many other tasks
(-) looks like cgi's, and is
(?) really a compute server
(+) http-based -> standard protocols
(+) mime-oriented -> compatible with existing apps
(-) not oopish, no toolkit interface
(-) not database-oriented
(+) looks like cgi's, but isn't
(?) good fit with web, really a image server