I don't see how there could be any other state visible.  How would you
find it other than through the req and res objects?  They are the only
things given to you.


On Thu, Dec 27, 2012 at 2:55 PM,  <martin.herbe...@education.ky.gov> wrote:
> Hi,
>
> I expect there is something written on this already, and I'd be happy to be
> pointed to it.  I haven't figured out what search keywords to use.
>
> As I understand it, a nodejs process may be dealing with multiple requests
> concurrently.  In an http scenario, user 1's request/response objects may be
> inactive - perhaps waiting for a DBMS query to complete - when user 2's http
> request is received.  These are not handled by independent, synchronous
> threads, but some sort of state/session data/objects/handles are kept
> separate for user 1's request and user 2's request - otherwise node would
> not know which TCP connection should get the query results, etc.
>
> So is everything related to each request encapsulated with the
> request/response objects or object instances?  Or is there other "state"
> related stuff  that is visible somewhere?
>
> thanks
>
> Martin
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to