Fork me on GitHub
#ring
<
2017-06-02
>
isaac05:06:05

IMO, the ring should use namespaced keys, eg. :ring/body, :ring/headers

seancorfield06:06:34

isaac: The Ring spec predates the recent popularity of namespaced keywords.

weavejester14:06:01

It’s something I’m planning to put forward for Ring 2.0, though the namespaces will be :ring.request/* and :ring.response/*.

isaac06:06:39

👍 that would be better

isaac06:06:18

I think also, ring should use deferred to support asynchronize, instead of arity of handler

weavejester22:06:51

deferred from Manifold?

weavejester22:06:10

Manifold is a significant size - it’s larger than Ring itself.

weavejester22:06:22

And others might want to use different async systems.

weavejester22:06:46

Ring uses the lowest-common-denominator. The simplest async solution that can be translated into any other async system.

weavejester22:06:10

If you want to use deferreds instead of the three-arity syntax, then it’s just three lines of middleware away.

isaac01:06:09

actually, I like more async, I use promise-chan support asynchronization in my app internally. 🙂

weavejester03:06:43

Adding promise-chan support is also just a middleware away 🙂