Re: CGI and SSI

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 45422
interpreted = N
texte = Hi Frank, Well, I have to say that that SSI description is even crapper than mine!! What a load of stink. It's too long anyway... it's like calling a 'pencil' a 'lead-based writing implement', and it seems to only be defining the include tag and not all the other ones. Whatever webserver you're running will probably have a description of available SSI tags. In terms of whether it's proper to use those terms re WebDNA: personally I don't care and am not going to lose much sleep over it. ;-) I'm not much of a terminology nazi. Maybe someone else on the list is?Regards,TimOn Tuesday, 19 November 2002 12:23 PM, Frank Nordberg wrote:>>>Tim Robinson wrote:>> SSI stands for Server Side Include. These are basically tags>associated with your webserver. Standard SSIs being for date,>include file (in the form ), and counters all of which can be done with WebDNA.>> >> CGI stands for Common Gateway Interface. I believe it usually>refers to CGI scripts created in Perl to control forms actions,>but I've heard a lot of people talking about CGI as any>middleware app. So by that definition, WebDNA is CGI...>probably depends on who publishes your geek dictionary....>>>Thanks Tim, I can use those descriptions. It doesn't answer my main >question, though>The Online Computing Dictionary at http://www.instantweb.com/ defines >SSI as:>The facility provided by several HTTP servers, e.g. NCSA httpd, to >replace certain HTML tags in one HTML file with the contents of another >file at the time when the file is sent out by the server, i.e. an HTML >macro.>>and CGI as:>A standard for running external programs from a World-Wide Web HTTP >server. CGI specifies how to pass arguments to the executing program as >part of the HTTP request. It also defines a set of environment >variables. Commonly, the program will generate some HTML which will be >passed back to the browser but it can also request URL>redirection.>>WebDNA does everything you'd expect from a SSI from a CGI application, >but the way it works, doesn't seem to fit the strict definitions. So is >it proper to use those two terms when we're talking about>WebDNA?>>Frank Nordberg>http://www.musicaviva.com>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://search.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: CGI and SSI (Dan Strong 2002)
Re: CGI and SSI (John Peacock 2002)
Re: CGI and SSI (Kenneth Grome 2002)
Re: CGI and SSI (Alan White 2002)
Re: CGI and SSI (Tim Robinson 2002)
Re: CGI and SSI (Frank Nordberg 2002)
Re: CGI and SSI (Tim Robinson 2002)
CGI and SSI (Frank Nordberg 2002)

Hi Frank, Well, I have to say that that SSI description is even crapper than mine!! What a load of stink. It's too long anyway... it's like calling a 'pencil' a 'lead-based writing implement', and it seems to only be defining the include tag and not all the other ones. Whatever webserver you're running will probably have a description of available SSI tags. In terms of whether it's proper to use those terms re WebDNA: personally I don't care and am not going to lose much sleep over it. ;-) I'm not much of a terminology nazi. Maybe someone else on the list is?Regards,TimOn Tuesday, 19 November 2002 12:23 PM, Frank Nordberg wrote:>>>Tim Robinson wrote:>> SSI stands for Server Side Include. These are basically tags>associated with your webserver. Standard SSIs being for date,>include file (in the form ), and counters all of which can be done with WebDNA.>> >> CGI stands for Common Gateway Interface. I believe it usually>refers to CGI scripts created in Perl to control forms actions,>but I've heard a lot of people talking about CGI as any>middleware app. So by that definition, WebDNA is CGI...>probably depends on who publishes your geek dictionary....>>>Thanks Tim, I can use those descriptions. It doesn't answer my main >question, though>The Online Computing Dictionary at http://www.instantweb.com/ defines >SSI as:>The facility provided by several HTTP servers, e.g. NCSA httpd, to >replace certain HTML tags in one HTML file with the contents of another >file at the time when the file is sent out by the server, i.e. an HTML >macro.>>and CGI as:>A standard for running external programs from a World-Wide Web HTTP >server. CGI specifies how to pass arguments to the executing program as >part of the HTTP request. It also defines a set of environment >variables. Commonly, the program will generate some HTML which will be >passed back to the browser but it can also request URL>redirection.>>WebDNA does everything you'd expect from a SSI from a CGI application, >but the way it works, doesn't seem to fit the strict definitions. So is >it proper to use those two terms when we're talking about>WebDNA?>>Frank Nordberg>http://www.musicaviva.com>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://search.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Tim Robinson

DOWNLOAD WEBDNA NOW!

Re: CGI and SSI

2002

Top Articles:

Related Readings: