Hi Marnen, > What do you need a tutorial for? It's easy to use a Web browser or a > tool like curl to send an arbitrarily crafted GET or POST request that > never came from your form but looks as if it did. That's just the way > that a stateless protocol like HTTP works: each request is its own > universe and (absent hacks like cookies) doesn't keep track of what the > last request was.
Thanks. I'm finally getting that idea through my thick skull. As I said to another respondent, I was using the Desktop-Programming model in the stateless Internet-Programming environment. Thanks to you, et al, for getting that cleared up for me. Best wishes, Richard On Aug 9, 11:16 am, Marnen Laibow-Koser <[email protected]> wrote: > RichardOnRails wrote: > > Hi Hassan, > > >> > It can't be nil. When the form is instantiated > > >> Assuredly, it can be -- a request can be generated without your form > >> being involved at all. > > > I don't get it. Can you point me to some tutorial that deals with > > this issue? > > What do you need a tutorial for? It's easy to use a Web browser or a > tool like curl to send an arbitrarily crafted GET or POST request that > never came from your form but looks as if it did. That's just the way > that a stateless protocol like HTTP works: each request is its own > universe and (absent hacks like cookies) doesn't keep track of what the > last request was. > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
