Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!swrinde!emory!darwin.sura.net!blaze.cs.jhu.edu!not-for-mail From: bogstad@news.cs.jhu.edu (Bill Bogstad) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Was: Future of FreeBSD..: HTML for GUI ? Date: 4 Aug 1995 07:14:08 GMT Organization: Johns Hopkins University, Computer Sciene Department Lines: 27 Message-ID: <3vshc0$cji@blaze.cs.jhu.edu> References: <3vgtgs$ti1@nntpd.lkg.dec.com> <3vo8l5$90d@mars.earthlink.net> <3vpr70$es8@agate.berkeley.edu> NNTP-Posting-Host: rhombus.cs.jhu.edu In article <3vpr70$es8@agate.berkeley.edu>, Jordan K. Hubbard <jkh@violet.berkeley.edu> wrote: >In article <3vo8l5$90d@mars.earthlink.net>, >Robert Nusbaum <rnusbaum@earthlink.net> wrote: >>HTML is the agreed upon method of passing messages >>between client and server. The problem now is the >>need for CGI programming on the server. All > >Ya know, I wonder about that. It seems almost ludicrous in some cases to >bring up a full WWW server and write the glue code as CGI scripts which >just, in turn, spit out HTML files someplace else for the sole consumption >of the browser. Wouldn't it make more sense to start with the stuff >distributed by w3.org and develop an embedable library for giving >an application its own direct httpd capability? Heck, you could export >the "httpd library" API through TCL, make the server application also >export some TCL API and then just write companion tcl scripts to >glue the server to the browser clients - much more easily extensible >and at a much higher level than CGI. > >Wondering what the heck I'm talking about? No. Sounds like what the authors of SATAN did as a special case. Except, I believe they wrote most of it in Perl. Generalizing it to a library would be nice though... Bill Bogstad bogstad@cs.jhu.edu