https://bugzilla.wikimedia.org/show_bug.cgi?id=25676
--- Comment #19 from Neil Kandalgaonkar <[email protected]> 2011-03-28 17:48:19 UTC --- (In reply to comment #18) I agree with most everything Michael wrote, except: > Success > chunks respond with partial data revived i.e HTTP/1.1 308 Resume Incomplete > headers which also set the byte range the next chunk. While I personally believe that using HTTP Headers and statuses like this is The Right Thing, this tends not to work in APIs that are designed for the masses. And we would like this API to be reimplemented by others. It is difficult to underestimate the level of incompetence out there when it comes to the web. Your average developer has no idea how to write a library that traps a 308 status. Generally people prefer a RPC-like model, with both success and error statuses encoded into 200 OK responses. :( And, that's already what the rest of the MediaWiki API does. Much like Flickr's similar RPC-oriented API is widely implemented, despite many flaws. Because it is that simple, people can dash off a client in an afternoon. > Checksums for individual chunks may be overkill Okay. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
