On Tue, Dec 2, 2008 at 7:58 PM, e deleflie <[EMAIL PROTECTED]> wrote:
>> I like the idea of one method called "upload",
> ... snip ...
>
> I was just going to put into question Jenna's suggestion of only one
> method. The question I was going to ask was ... what is the advantage,
> and to whom for only having 1 method used for 2 different kinds of
> posts ...( the "form post" and the "REST post").
I'm not clear on what distinction you see with "form post" versus
"REST post". You can post a form while adhering to REST principles.
Maybe I have a different notion of a form? It seems to me like you are
always posting a form. It might just be one with a single implicit
key/value pair(e.g. upload file, :to => location) as opposed to an
explicit group of them(e.g. upload :fields => { ... }). Again, I don't
know that I have all the concepts clear in my head here.. it doesn't
help to keep talking about post the action and POST the HTTP method..
:P
> It might be good for the implementing developer, for writing less
> implementation code, for test cases, and for consiseness of
> documentation... but is it clearer for the user of that method?
>
> Maybe it is.
Yeknow, I was thinking over this just now as I made and consumed a
delicious sandwich, and I actually wonder if it should just be ONE
method. One method for making HTTP requests. One of the things that
made me think of this was in pondering REST interfaces and wondering..
which of these two methods would handle DELETE? Neither download() nor
upload() feels quite right in either case.
I don't know what a single method would be called. request? http? go_net_go?
-shrugs-
This isn't even behavior I need, yet, so I'm just another backseat
driver for now, I guess. ;)
--
Seth Thomas Rasmussen
http://greatseth.com
