Jake Goulding

> a different algorithm Yeah, I'll skim through and see if anything jumps out as a key match. One nice thing is that you and I can collaborate on ideas...

@dtolnay how is Serde handling similar issues?

For the purposes of the playground, I need [this specific configuration](https://github.com/integer32llc/rust-playground/blob/062e960b02f0e0438561ecff831b9560149bbf9a/ui/src/main.rs#L120-L131): ```rust chain.link_around(CorsMiddleware { // A null origin occurs when you make a request from a // page hosted on...

As general background, we mostly followed [corsware](https://crates.io/crates/corsware)'s lead on this because that best matched with *my* needs for the playground. It's certainly possible there are better ways! > responses on...

> try this on a real application How would your application make use of the `Config`?

> more failure cases due to parsing. Perhaps worth looking into [typed-headers](https://github.com/sfackler/typed-headers) (specifically [this pull request](https://github.com/sfackler/typed-headers/pull/3)) to leverage some of the parsing.

Or at [hyperx](https://docs.rs/hyperx/0.13.1/hyperx/header/index.html)

It feels like allowing only attributes would be highly resistant to reuse. For example, I believe I need CORS for these endpoints; note that there are endpoints across `impl`s: ```rust...

The playground uses Serde outside of just the web frontend, so I'd be loathe to remove this import as it actually is a dependency of ours.

> What happens if you import serde derive before tower? That's actually what I was doing. However, importing `serde_derive` *after* `tower_web` does seem to squelch the warning. Presumably `tower_web`'s other...