[#20675] RCR: non-bang equivalent to []= — Tobias Reif <tobiasreif@...>

Hi,

49 messages 2001/09/01
[#20774] Re: RCR: non-bang equivalent to []= — Tobias Reif <tobiasreif@...> 2001/09/03

I wrote:

[#20778] Re: RCR: non-bang equivalent to []= — Kevin Smith <kevinbsmith@...> 2001/09/03

--- Tobias Reif <tobiasreif@pinkjuice.com> wrote:

[#20715] oreilly buch von matz - website online — markus jais <info@...>

hi

43 messages 2001/09/02
[#20717] Re: OReilly Ruby book has snail on cover — ptkwt@...1.aracnet.com (Phil Tomson) 2001/09/02

Actually, thanks for posting it here. I was trying to search OReilly's

[#20922] Re: OReilly Ruby book has snail on cover — Paul Brannan <pbrannan@...> 2001/09/05

On Mon, 3 Sep 2001, Phil Tomson wrote:

[#20768] Minor cgi.rb question — "Hal E. Fulton" <hal9000@...>

I don't have much experience with

25 messages 2001/09/03

[#20770] Calling member methods from C++ — jglueck@... (Bernhard Glk)

Some quetsions have been solved for me, but my message system does not

12 messages 2001/09/03

[#20976] destructor — Frank Sonnemans <ruby@...>

Does Ruby have a destructor as in C++?

25 messages 2001/09/07

[#21218] Ruby objects <-> XML: anyone working on this? — senderista@... (Tobin Baker)

Are there any Ruby analogs of these two Python modules (xml_pickle,

13 messages 2001/09/15

[#21296] nested require files need path internally — Bob Gustafson <bobgus@...>

Version: 1.64

29 messages 2001/09/18
[#21298] Re: nested require files need path internally — David Alan Black <dblack@...> 2001/09/18

Hello --

[#21302] Re: nested require files need path internally — Bob Gustafson <bobgus@...> 2001/09/18

On Tue, 18 Sep 2001, David Alan Black wrote:

[#21303] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21306] Re: nested require files need path internally — Lars Christensen <larsch@...> 2001/09/18

On Tue, 18 Sep 2001, Yukihiro Matsumoto wrote:

[#21307] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21331] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/18

> The big difference is C++ search done in compile time, Ruby search

[#21340] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21353] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/18

On Wed, 19 Sep 2001, Yukihiro Matsumoto wrote:

[#21366] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/19

Hi,

[#21368] Re: nested require files need path internally — "Julian Fitzell" <julian-ml@...4.com> 2001/09/19

On 19/09/2001 at 10:12 AM matz@ruby-lang.org wrote:

[#21376] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/19

Hi,

[#21406] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/19

On Wed, 19 Sep 2001, Yukihiro Matsumoto wrote:

[#21315] Suggestions for new CGI lib — anders@... (Anders Johannsen)

From the comp.lang.ruby thread "Minor cgi.rb question" (2001-09-03), I

21 messages 2001/09/18

[#21413] Ruby/objects book in style of The Little Lisper — Brian Marick <marick@...>

I fell in love with Lisp in the early 80's. Back then, I read a book called

36 messages 2001/09/19
[#21420] Re: Ruby/objects book in style of The Little Lisper — Christopher Sawtell <csawtell@...> 2001/09/20

On 20 Sep 2001 06:19:44 +0900, Brian Marick wrote:

[#21479] Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/21

--- Christopher Sawtell <csawtell@paradise.net.nz> wrote:

[#21491] SV: Re: Ruby/objects book in style of The Little Lisper — "Mikkel Damsgaard" <mikkel_damsgaard@...> 2001/09/21

[#21494] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/21

--- Mikkel Damsgaard <mikkel_damsgaard@mailme.dk> wrote:

[#21510] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Todd Gillespie <toddg@...> 2001/09/22

On Sat, 22 Sep 2001, Kevin Smith wrote:

[#21514] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/22

--- Todd Gillespie <toddg@mail.ma.utexas.edu> wrote:

[#21535] irb — Fabio <fabio.spelta@...>

Hello. :) I'm new here, and I have not found an archive of the previous

15 messages 2001/09/22

[#21616] opening a named pipe? — "Avdi B. Grimm" <avdi@...>

I'm having trouble reading from a named pipe in linux. basicly, I'm

12 messages 2001/09/24

[#21685] manipulating "immutable" objects such as Fixnum from within callbacks & al... — Guillaume Cottenceau <gc@...>

Hello,

15 messages 2001/09/25

[#21798] Ruby internal (guide to the source) — "Benoit Cerrina" <benoit.cerrina@...>

Hi,

22 messages 2001/09/28

[ruby-talk:21315] Suggestions for new CGI lib

From: anders@... (Anders Johannsen)
Date: 2001-09-18 13:22:30 UTC
List: ruby-talk #21315
From the comp.lang.ruby thread "Minor cgi.rb question" (2001-09-03), I
gathered that some people disagree with the way the current 'cgi.rb'
is designed.

Incidently, the lack of consistensy in 'cgi.rb' has been my primary
reason for _not_ using Ruby as a web scripting language. Based on my
experience in web scripting, I have developed a working model for
'next generation' CGI, which may or may not be what we are looking
for.

Since it is a model, actual functionality is yet to be implemented. I
would appreciate a discussion of pros and cons in my suggestion.
Comments and improvements are most welcome.

The goals of design are to:

* Introduce the well-known 'Request/Response' model
* Separate Cookie, Post, Get and Environment namespaces
* Add support for 'plug-in' output handlers, thus making for example
gz compression of output easy.
* Use an open model to make integration with fastcgi/cgisock and
future technologies seamless
* Separate actual CGI and HTML generation, as they are two very
different matters (my suggestion only cover CGI)
-- while still maintaining 'ease-of-use'

The design is basically comprised by the following base classes, all
accessed through the instanciated CGI class (as indicated in the
comments)

CGI # cgi
CGI::Request # cgi.request
CGI::Request::Cookie # cgi.request.cookie
CGI::Request::Post # cgi.request.post
CGI::Request::Get # cgi.request.get
CGI::Request::Env # cgi.request.env
CGI::Request::Header # cgi.request.header
CGI::Request::Var # cgi.request.var
CGI::Response # cgi.response
CGI::Response::Cookie # cgi.response.cookie
CGI::Response::Header # cgi.response.header
CGI::Namespace # cgi.namespace
CGI::Output # cgi.output
CGI::Session # cgi.session

A practical example of usage could be:

CGI.new do |cgi|
  req = cgi.request
  req.cookie['user_var'] # Get the named cookie 'user_var'
  req.header['X-Something'] # Get the named header 'X-Something'
  req.var['user_var'] # Get the named variable 'user_var'. Cookie,
Post, Get, Env and Headers are merged in a configurable order

  # Add text to the output buffer
  cgi << " TEST "

  # Set a custom cookie and header in the response
  cgi.response.cookie.set ("name", "content")
  cgi.response.header.set ("name", "content")

  # Set output options
  cgi.output.handler = call_back
  cgi.output.stream  = $stdout

  # Introduce new namespace with the indicated variables exported
(non-existant variables is   nil)
  cgi.namespace.var do
    unless non_existant_var.nil?
      # Do stuff
    end
  end   
    
end # At the end of the block, cgi.print is automatically called

Let me know you think.

Best regards,
Anders Johannsen
Denmark

In This Thread

Prev Next