On 17 April 2013 22:33, Brian Wolff bawo...@gmail.com wrote:
My understanding is its not really possible to do this in php in a way
that would actually be of use to anyone. See
https://bugzilla.wikimedia.org/show_bug.cgi?id=26631#c1
Still, supporting this in a way “that wouldn’t be of use”,
On 2013-04-18 1:13 AM, Petr Kadlec petr.kad...@gmail.com wrote:
On 17 April 2013 22:33, Brian Wolff bawo...@gmail.com wrote:
My understanding is its not really possible to do this in php in a way
that would actually be of use to anyone. See
On Tue, Apr 16, 2013 at 11:50 PM, Tyler Romeo tylerro...@gmail.com wrote:
Found this interesting articles on designing an API for what it's worth.
Thought some people my find it interesting.
http://mathieu.fenniak.net/the-api-checklist/
Some thoughts:
#2: HTTP Basic authentication is simple,
Regarding #7 in that list (Expect: 100-Continue), I think it would be nice
if Wikimedia wikis did this.
I know that at least in .Net, if I send a POST request to
http://en.wikipedia.org/w/api.php,
the Expect: 100-Continue header will be set, which results in an 417
Expectation failed error.
.Net
On Wed, Apr 17, 2013 at 4:18 PM, Petr Onderka gsv...@gmail.com wrote:
Regarding #7 in that list (Expect: 100-Continue), I think it would be nice
if Wikimedia wikis did this.
I know that at least in .Net, if I send a POST request to
http://en.wikipedia.org/w/api.php,
the Expect: 100-Continue
My understanding is its not really possible to do this in php in a way
that would actually be of use to anyone. See
https://bugzilla.wikimedia.org/show_bug.cgi?id=26631#c1
-bawolff
On 4/17/13, Petr Onderka gsv...@gmail.com wrote:
Regarding #7 in that list (Expect: 100-Continue), I think it
I didn't necessarily mean that the 100-Continue workflow should be fully
supported.
I think Ignoring the header would be much better than completely refusing
to work with it (and replying with error 417) and my guess is that doing
that should be possible.
Looking at the HTTP specification [1], it
So you're suggesting we go *against* the HTTP standard? That's not exactly
what you're supposed to do.
Well, ignoring the header makes more sense to me and, personally, I would
prefer that behavior.
But it's a minor issue and I think going against the standard is not
actually worth it.
Petr
On Wed, Apr 17, 2013 at 4:47 PM, Petr Onderka gsv...@gmail.com wrote:
I didn't necessarily mean that the 100-Continue workflow should be fully
supported.
I think Ignoring the header would be much better than completely refusing
to work with it (and replying with error 417) and my guess is
Found this interesting articles on designing an API for what it's worth.
Thought some people my find it interesting.
http://mathieu.fenniak.net/the-api-checklist/
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com |
Thanks Tyler, some points are very interesting.
On Wed, Apr 17, 2013 at 5:50 AM, Tyler Romeo tylerro...@gmail.com wrote:
Found this interesting articles on designing an API for what it's worth.
Thought some people my find it interesting.
http://mathieu.fenniak.net/the-api-checklist/
*-- *
11 matches
Mail list logo
