Julian Arni

I've come across the same problem. Encoding different CSVs and then merging them is expensive. Having the ability to decide (in, presumably, `EncodeOptions`) how to encode headers that are missing...

@alexanderkjeldaas are the middleware options sufficient? If so, can we close this? (I also don't quite understand your last comment. Do you mean we should have `servant-client` do leg work...

OK, I see. Given that rate-limiting would show up (a) in the server, (b) in the documentation, and (c) in clients, I see the advantage of having a combinator rather...

This will get a lot easier with #327 for `servant-server`.

@sachs4 nice. I have a couple of questions or comments: 1) I think our experience has been that adding a single combinator with more configuration options (and then possibly type...

Great news! Re: should-not-typecheck. I don't know any fix, but you can use `doctest` to verify type errors exist and say what you expect. I've been thinking about moving away...

Thanks a lot for this! What users actually are exposed to seems like the right direction to me. Some notes: - From what I can tell, the above will only...

CORS is pretty messy... One issue with the Verb design, I now realize, is that it doesn't work if the browser doesn't send an Access-Control-Request-Method, since the leaf can't look...

> The other trick is that CORS data should be non-specific to Options headers but instead to endpoints in the tree, which don't really have direct representation in Servant. Options...

Javascript code generation should be relatively simple *if* we can make a simplifying assumption that we never get into trouble for sending cookies and headers to endpoints that might not...