Re:/dev/null as a Service
by bad_user on Tuesday October 29, 2013 @06:57PM
(#6638118)
I think it should be "204 No Content".
[ Parent
| on HN ]
200 for a POST, 204 for a GET.
I second this one! makes more sense than plain 200.
Re:/dev/null as a Service
by darkchasma on Tuesday October 29, 2013 @07:22PM
(#6638259)
I can't believe you guys are debating the correct HTTP return code for a joke service? Besides, it's obviously 200.
These provide great opportunities for better understanding return codes.
Besides, for POST it is obviously 202 ACCEPTED
Does it discard data in a manner compliant with FIPS 140-2? Or NIST SP800-88?
Wait... is it a joke?
I hope not, I've been depending on this service for a while. I have it integrated via FUSE on my prod servers.
We did have some problems of blocking on large files, which is less than ideal for a /dev/null service.
After dealing with their customer support (which has been super helpful), we are looking to move to a named pipe / FIFO.. Which will non-block and cache lolcally, with a watcher service to push it to their site.
Happy Customer, A+++, would recommend.
Re:/dev/null as a Service
by general_failure on Tuesday October 29, 2013 @09:33PM
(#6638862)
Well with the planned dev/random support, this is going to kick ass.