CGI is merely the protocol your web browser is using to communicate
with the Rails server.  You are absolutely using CGI.

Bill


On Thu, 31 Mar 2005 05:14:45 +0900, JZ <spamerom / niet.com> wrote:
> Dnia Wed, 30 Mar 2005 22:24:30 +0900, Austin Ziegler napisaa):
> 
> > There is no problem with Ruby and CGI (or much of anything else).
> > Ruwiki is a decently fast wiki application written in Ruby. There is
> > a problem with Rails and CGI, because the basic philosophy of Rails
> > is different.
> >
> > Rails is best considered an application server, and as such is
> > expected to be running on your system full time (as far as I can
> > tell, it doesn't). Otherwise, you have to go through its extensive
> > compile process every time -- no, Ruby doesn't do bytecodes or
> > bytecode caching at this point.
> 
> I sth do not understand. Did I really execute Rails through CGI??? I
> thought I executed long-running process of Rails through "ruby.exe
> scripts\server" command. And CGI, as I thought, was only small adapter
> between Apache and Rails application server.
> E.g. Webware can work in that way. CGI is used only as a bridge between
> Apache and long-running Webkit applications server. It works very fast.
> 
> --
> JZ
> 
> 


-- 
$stdout.sync = true
"Just another Ruby hacker.".each_byte do |b|
  ('a'..'z').step do|c|print c+"\b";sleep 0.007 end;print b.chr
end; print "\n"