Reconsider `:aleph/`-namespaced keywords about aleph HOT 3 OPEN

One thing we could do is stick all internal keys in a map under a single key, like:

{:headers {...}
 :body ...
 :aleph/keep-alive? true
 :aleph/request-arrived some-nano-time
 :aleph/internal {:ch ch 
                  :gory-internal1 ...
                  :gory-internal2 ...}}

I think it's nice and tidy this way.

from aleph.

I think I slightly prefer the flat version because looking up a single internal key is more convenient then (most usage sites are only interested in one of them at a time I think). But the submap approach has the nice advantage that endusers can just dissoc that single key to rid the request map of the gory internals, so there's that.

Another alternative could be to store these in metadata (cf. how it's done for :aleph/channel on streams in the UDP, TCP and websocket implementations).

from aleph.

Flat version is fine, I don't care that much.

Please do not store them in metadata though. I've been wanting to remove that behavior because it violates expectations about what metadata is, and what it's attached to.

from aleph.