Judson Lester

Some of the motivation to convert to Tokio 0.12 was in service of being able to connect the Service to different HTTP servers, and therefore into a HTTPS server. The...

That was my error, and not an intentional change to `master` I'd :+1: protecting master, if only from that.

I'd agree to this in general, but I wonder if it isn't a symptom of the "Into" happening at the wrong level. If e.g. we took a Result and produced...

One fresh look here: a very reasonable place for a consumer app to handle Accept is in IntoRespone implementations. On the other hand, it's possible that different content types would...

I'd think that the thing to do really is a documentation change - add comments to the examples themselves, or their READMEs or the README in the top level examples...

Is there a reason that Gotham hasn't switched to 0.12 and `http`? Are they not stable Rust yet?

I totally missed #7. From experience implementing this kind of thing, the routes do need some fully-qualified identifier - names are the most obvious solution. If they associate to a...

Is this equivalent to "PlatformSpecific" is not very useful event information? I was looking at fswatch to drive some build processes, but I get (I think?) events for file _access_...

Using the inotify under Linux iirc. I was seeing PlatformSpecific unaccompanied by other useful events, and in reaction to write/create

All that said, would it be impossible to include a system-specific identifier for those?