P
paul vudmaska
Hi All!
My first post - i've just signed up for the list and
here i find out about the conference in Austin. I live
on canyon lake 45 minutes away. How cool is that? Free
room and board for the weekend for only $999 american
per night.<g> Less for female hotties. Really if yor
are strapped, drop me an e.
Anyway the reason i signup up was this. I'm a M$
developer, for about 6 years, trying to slide into
something cool and ruby seems to me a good server side
tool, along with its obvious other attributes.
However, i've run into some problems - mostly with the
CGI module. I mean no offense, and, really, am not
qualified to say, but i'm having some difficulty,
technically(mostly) and philisophically. Please
comment on or correct any assumptions i make below.
1) Getting a post/get param, brings me an array by
default whether i like it or not?
2) I can not differentiate between a get and a post?
ie: CGI::Request.Form(param);
CGI::Request.QueryString(param) or something like
that?
3) Sessions, do i need to roll an id for each session?
If so, should this not be a part of the module? Not as
important...thinking... what about pickling?
(maintaining an object between requests)
If i could program my way out of a paper bag i would
not be doing web programming and might jump right into
CGI.rb and fix/alter/augment these things to suit
myself but was wondering if others have had similar
first rides with web ruby.
TBH, ASP's <duck> request / response loop is quite
intuitive and might be considered useful for
implementation ideas in ruby.
Form:Request.Form('param')
QString:Request.QueryString('param')
Either : Request('param') # post takes priority
if Session('param')
param = Session('param')
else
param = Session.new('param')
end
Or something. IMO, CGI will be critical to the success
of server-side ruby and if we all go off rolling our
own it may fracture a cornerstone of the tool...and
leave a lot of code dangling when sharing components.
Just some thots, thanks!
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
My first post - i've just signed up for the list and
here i find out about the conference in Austin. I live
on canyon lake 45 minutes away. How cool is that? Free
room and board for the weekend for only $999 american
per night.<g> Less for female hotties. Really if yor
are strapped, drop me an e.
Anyway the reason i signup up was this. I'm a M$
developer, for about 6 years, trying to slide into
something cool and ruby seems to me a good server side
tool, along with its obvious other attributes.
However, i've run into some problems - mostly with the
CGI module. I mean no offense, and, really, am not
qualified to say, but i'm having some difficulty,
technically(mostly) and philisophically. Please
comment on or correct any assumptions i make below.
1) Getting a post/get param, brings me an array by
default whether i like it or not?
2) I can not differentiate between a get and a post?
ie: CGI::Request.Form(param);
CGI::Request.QueryString(param) or something like
that?
3) Sessions, do i need to roll an id for each session?
If so, should this not be a part of the module? Not as
important...thinking... what about pickling?
(maintaining an object between requests)
If i could program my way out of a paper bag i would
not be doing web programming and might jump right into
CGI.rb and fix/alter/augment these things to suit
myself but was wondering if others have had similar
first rides with web ruby.
TBH, ASP's <duck> request / response loop is quite
intuitive and might be considered useful for
implementation ideas in ruby.
Form:Request.Form('param')
QString:Request.QueryString('param')
Either : Request('param') # post takes priority
if Session('param')
param = Session('param')
else
param = Session.new('param')
end
Or something. IMO, CGI will be critical to the success
of server-side ruby and if we all go off rolling our
own it may fracture a cornerstone of the tool...and
leave a lot of code dangling when sharing components.
Just some thots, thanks!
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
