Skip to content
This repository was archived by the owner on Dec 27, 2024. It is now read-only.

Zonejs Integration #56

Open
etsuo opened this issue Apr 19, 2017 · 1 comment
Open

Zonejs Integration #56

etsuo opened this issue Apr 19, 2017 · 1 comment
Labels

Comments

@etsuo
Copy link
Member

etsuo commented Apr 19, 2017

Each request should be it's own zone context. This will allow for shared state through a request... for example a DB handling function that doesn't have access to express.Request would still have access to the current zone context for the purpose of exchange data across that request.

... https://expressjs.com/en/4x/api.html#res.locals
The advantage of using zones is that we won't have to pass around a reference to res.locals in functions that otherwise wouldn't have access to that.

See:

@etsuo etsuo added this to the 0.5.0 milestone Apr 19, 2017
@etsuo etsuo modified the milestone: 0.5.0 May 16, 2017
@etsuo
Copy link
Member Author

etsuo commented Feb 8, 2018

I'm developing doubts that this should be a core implementation... If someone really wants Zonejs they could inject it in their own middleware early on, so it may not make sense to burden all users with this as many may not find it desirable.

@etsuo etsuo removed the feature label Feb 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant