| Time |
S |
Nick |
Message |
| 01:08 |
|
|
shrink0r_ joined #rest |
| 02:37 |
|
|
ewalti_ joined #rest |
| 02:41 |
|
|
warehouse13 joined #rest |
| 03:37 |
|
|
ewalti joined #rest |
| 03:50 |
|
|
ironChicken joined #rest |
| 03:53 |
|
|
lemur joined #rest |
| 06:35 |
|
|
ewalti joined #rest |
| 06:35 |
|
|
ewalti joined #rest |
| 06:36 |
|
|
ewalti joined #rest |
| 07:08 |
|
|
ewalti joined #rest |
| 07:09 |
|
|
ewalti joined #rest |
| 07:12 |
|
|
ewalti joined #rest |
| 07:15 |
|
|
ewalti joined #rest |
| 07:26 |
|
|
_ollie joined #rest |
| 07:53 |
|
|
ewalti joined #rest |
| 07:57 |
|
|
ewalti joined #rest |
| 08:03 |
|
|
17SAB04RE joined #rest |
| 08:03 |
|
|
azer_ joined #rest |
| 08:03 |
|
|
ewalti joined #rest |
| 08:05 |
|
|
ewalti joined #rest |
| 08:09 |
|
|
ewalti joined #rest |
| 08:10 |
|
|
azer_ joined #rest |
| 08:10 |
|
|
ewalti joined #rest |
| 08:14 |
|
|
ewalti joined #rest |
| 08:15 |
|
|
ewalti joined #rest |
| 08:15 |
|
|
_ollie joined #rest |
| 08:31 |
|
|
Andre-B joined #rest |
| 09:03 |
|
|
ewalti joined #rest |
| 09:04 |
|
|
ewalti joined #rest |
| 09:07 |
|
|
ewalti joined #rest |
| 09:08 |
|
|
ewalti joined #rest |
| 09:11 |
|
|
ewalti joined #rest |
| 09:11 |
|
|
ewalti joined #rest |
| 09:12 |
|
|
ewalti joined #rest |
| 09:12 |
|
|
ewalti joined #rest |
| 09:14 |
|
|
ewalti joined #rest |
| 09:14 |
|
|
ewalti joined #rest |
| 09:18 |
|
|
ewalti joined #rest |
| 09:20 |
|
|
ewalti joined #rest |
| 09:21 |
|
|
ewalti joined #rest |
| 09:22 |
|
|
ewalti joined #rest |
| 09:23 |
|
|
ewalti joined #rest |
| 09:23 |
|
|
ewalti joined #rest |
| 09:24 |
|
|
ewalti joined #rest |
| 09:25 |
|
|
ewalti joined #rest |
| 09:29 |
|
|
ewalti joined #rest |
| 09:31 |
|
|
sulky joined #rest |
| 09:35 |
|
|
Left_Turn joined #rest |
| 09:37 |
|
|
ewalti joined #rest |
| 09:41 |
|
|
shrink0r joined #rest |
| 09:43 |
|
|
dEPy joined #rest |
| 09:57 |
|
|
ewalti joined #rest |
| 10:12 |
|
|
ewalti joined #rest |
| 10:13 |
|
|
ewalti joined #rest |
| 10:14 |
|
|
ewalti joined #rest |
| 10:16 |
|
|
ewalti joined #rest |
| 10:17 |
|
|
ewalti joined #rest |
| 10:18 |
|
|
ewalti joined #rest |
| 10:19 |
|
|
ewalti joined #rest |
| 10:21 |
|
|
ewalti joined #rest |
| 10:26 |
|
|
ewalti joined #rest |
| 10:27 |
|
|
ewalti joined #rest |
| 10:28 |
|
|
ewalti joined #rest |
| 10:30 |
|
|
ewalti joined #rest |
| 10:31 |
|
|
ewalti joined #rest |
| 10:32 |
|
|
ewalti joined #rest |
| 10:32 |
|
|
ewalti joined #rest |
| 10:38 |
|
|
ewalti joined #rest |
| 10:50 |
|
|
7GHAA3IOL joined #rest |
| 11:07 |
|
|
azer_ joined #rest |
| 11:34 |
|
|
mezod joined #rest |
| 13:04 |
|
|
mgomezch_ joined #rest |
| 13:15 |
|
|
azer_ joined #rest |
| 15:51 |
|
|
dEPy joined #rest |
| 16:15 |
|
|
igitoor joined #rest |
| 16:15 |
|
|
jgornick joined #rest |
| 16:30 |
|
|
igitoor joined #rest |
| 17:04 |
|
|
jsys joined #rest |
| 17:05 |
|
jsys |
Gotta love talks titles like "Word puns for the REST of us" |
| 18:11 |
|
|
ewalti joined #rest |
| 18:14 |
|
|
fumanchu joined #rest |
| 18:17 |
|
|
Andre-B_ joined #rest |
| 18:49 |
|
ramsey |
What formats are people using for JSON error responses these days? |
| 18:52 |
|
fumanchu |
ad-hoc :( |
| 19:03 |
|
|
spaceone joined #rest |
| 19:04 |
|
jsys |
ramsey: I have a specific format but not because it's standard as much, more because it's useful |
| 19:05 |
|
jsys |
ramsey: whenever I return an error code I return a JSON array "log" which is a list of events, each with a 1) code 2) message 3) path (input variable path for ex. 4) machine readable details 5) severity (info/warn/error) |
| 19:05 |
|
ramsey |
No one is actively using something like this? https://tools.ietf.org/html/draft-ietf-appsawg-http-problem-00 |
| 19:06 |
|
jsys |
ramsey: it's nice because you can map everything in that log - form field errors, whatever. |
| 19:06 |
|
jsys |
I actually stopped sending forms via HTML entirely. It's all XhR and logs in return |
| 19:07 |
|
jsys |
ramsey: a log could cover all the info shows in that draft without the XML bloat |
| 19:07 |
|
ramsey |
XML? |
| 19:08 |
|
ramsey |
I don’t see XML in the draft, except in the appendix |
| 19:08 |
|
jsys |
ramsey: it's pointless to use a standard error format, because you'll just spent days wondering how to map the standard to your needs. Pick one format for your entire project, and stick to it, is best IMHO |
| 19:09 |
|
jsys |
array<error> where error is {type: string, path: string, code: string, message: string, details: dict} |
| 19:09 |
|
ramsey |
I like standards. If more people adopt the same standards, then there are fewer integration pains to talk to multiple services. Better interoperability. Yadda yadda yadda. :-) |
| 19:10 |
|
jsys |
ramsey: that's the theory, but standards are never created; they can only be recognized. Trying to use an artificially created standard in the hope to obtain the benefits of a "real" one, is a bit like cargo cult-like |
| 19:10 |
|
* ramsey |
shrugs. I’m not sure what you’re trying to sell me on here. |
| 19:11 |
|
jsys |
ramsey: you can get the same benefit by simply using a simple format for all your resources in your API |
| 19:11 |
|
jsys |
ramsey: i.e. at least don't reinvent the format for every resource and verb |
| 19:11 |
|
jsys |
But other than that... |
| 19:13 |
|
jsys |
ramsey: I'm trying to "sell you" on pragmatism :P |
| 19:14 |
|
jsys |
Standards are useful for the network effects. No network effects, no benefits. |
| 19:15 |
|
ramsey |
Also useful so I don’t have to spend time thinking through an error format or argue minutiae of details with coworkers. |
| 19:17 |
|
jsys |
ramsey: that betrays you don't know what problem you have :P If you did, you'd have an idea of possible solutions, isn't this what we get paid for |
| 19:17 |
|
jsys |
ramsey: the problem is when you use a generic solution you don't get a solution for your problem, you get a solution for whatever problem the spec author thought he had |
| 19:18 |
|
jsys |
Think what info you want to communicate and come up with a format. |
| 19:18 |
|
jsys |
The log format I described I think it's quite flexible, but who knows. |
| 19:21 |
|
jsys |
ramsey: in the military when a problem is reported there's a rule the report should contain "all the W-s" like where, what, when. In computers we also have the problem we want information to be both human readable and machine readable. |
| 19:21 |
|
jsys |
So a format should cover all the Ws and cover both human and machine readable formats. |
| 19:23 |
|
jsys |
A message is a string for human consumption, containing all relevant info. Severity type is widely recognized as a used aspect to put in your errors (warning vs error). Code is required to seggregate errors by type. Path is needed for the "where" - was the error in the input, and which piece of input? And "details" is the information from the mes |
| 19:23 |
|
jsys |
sage in machine readable format "Password should be between 8 and 32 chars" path: "password" details: {length: [8, 32]} |
| 19:28 |
|
|
ewalti_ joined #rest |
| 20:35 |
|
|
lemur joined #rest |
| 21:35 |
|
|
vanHoesel joined #rest |
| 21:40 |
|
|
fumanchu joined #rest |
| 21:45 |
|
|
shrink0r joined #rest |
| 21:51 |
|
|
vanHoesel joined #rest |
| 22:20 |
|
|
shrink0r_ joined #rest |
