On Fri, Sep 28, 2007 at 03:22:23PM -0400, Nathaniel Talbott wrote:
> As far as I can tell, sending an actual HTTP PUT request to a Camping
> app will never parse the params out of the request body - or am I
> going nuts? This code seems to say only POST's will parse the request
> body:
>
> elsif
2007/9/27, why the lucky stiff <[EMAIL PROTECTED]>:
> Well, case-sensitiveness would be a prob with 1.5 as well. Since
> @env.HTTP_HOST will work and @env.http_host will not.
True. So what do you think of the attached patch ? It removes roughly
50 octets to camping.rb and seems to work pretty wel
On Fri, 2007-09-28 at 22:50 +0200, Jonas Pfenniger wrote:
> 2007/9/28, Nathaniel Talbott <[EMAIL PROTECTED]>:
> > As far as I can tell, sending an actual HTTP PUT request to a Camping
> > app will never parse the params out of the request body - or am I
> > going nuts?
>
> No you aren't at all. Ac
2007/9/28, Nathaniel Talbott <[EMAIL PROTECTED]>:
> As far as I can tell, sending an actual HTTP PUT request to a Camping
> app will never parse the params out of the request body - or am I
> going nuts?
No you aren't at all. Actually, Camping is only a toy to quickly hack
small apps together. I a
On 9/28/07, Nathaniel Talbott <[EMAIL PROTECTED]> wrote:
> It seems to me that most restful frameworks are assuming that you can
> PUT the same as you can POST, i.e. that other than the verb (and what
> you might do with it) the two will be treated the same.
This is a horrible Rails-ism, in my opi
On 9/28/07, Nathaniel Talbott <[EMAIL PROTECTED]> wrote:
> Of course, there's also the fact that while browsers don't *currently*
> support form verbs besides POST, I'm hopeful that that may change
> eventually.
Even if browsers do start supporting PUT requests, I'd be somewhat
shocked if they do
On 9/28/07, Lennon Day-Reynolds <[EMAIL PROTECTED]> wrote:
> I honestly wouldn't expect PUT (or any other HTTP actions other than
> GET, POST, and HEAD) to pass the input through a normal
> form-decoding step -- most of the time, the "payload" for a PUT is
> going to be XML, JSON, or even raw bina
On 9/28/07, Nathaniel Talbott <[EMAIL PROTECTED]> wrote:
> As far as I can tell, sending an actual HTTP PUT request to a Camping
> app will never parse the params out of the request body - or am I
> going nuts? This code seems to say only POST's will parse the request
> body:
>
> elsif @method ==
As far as I can tell, sending an actual HTTP PUT request to a Camping
app will never parse the params out of the request body - or am I
going nuts? This code seems to say only POST's will parse the request
body:
elsif @method == "post" and \
e.CONTENT_TYPE == "application/x-www-form-urlenc
2007/9/28, MenTaLguY <[EMAIL PROTECTED]>:
> Perhaps "condensing" ?
Yes, with a little touch of artistic sense added :)
Cheers,
zimbatm
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
On Fri, 28 Sep 2007 10:43:56 +0200, "Jonas Pfenniger" <[EMAIL PROTECTED]> wrote:
> I was referring to the action that consist of taking
> camping-unabridged.rb and create a "platter?" out of it. It is a
> reference to the visual output that camping.rb gives.
Perhaps "condensing" ?
-mental
__
2007/9/28, Matthew Snyder <[EMAIL PROTECTED]>:
> Running 'ruby beta.rb' produces no output and goes straight back to a
> prompt. Running 'ruby dispatch.fcgi' produces no output, and when I
> hit enter, I'm returned to a prompt.
> This is the only thing I get in my error logs:
> [Thu Sep 27 21:35:48
> I was referring to the action that consist of taking
> camping-unabridged.rb and create a "platter?" out of it. It is a
> reference to the visual output that camping.rb gives.
Ok, now I got it. That would be cool indeed.
Cheers,
Gregor
___
Camping-li
2007/9/28, Gregor Schmidt <[EMAIL PROTECTED]>:
> For a none native speaker. Could you give a synonym for "platterize".
Sorry, from a non native speaker too. The term was probably badly chosen.
I was referring to the action that consist of taking
camping-unabridged.rb and create a "platter?" out o
14 matches
Mail list logo
