Ok, that makes sense, thanks! Martin
On Friday, December 28, 2012 4:01:55 PM UTC-5, greelgorke wrote: > > the request+response objects hold links to the related connection, wich is > linked to the socket opened up on accept. > > all things are kept in the event loop, events and event handlers which > have links to related objects. this objects are either passed by as params > or via closure scope (or other qay of bypassing). so the state is kept in > the current state of the callback chain. > > Am Donnerstag, 27. Dezember 2012 23:55:20 UTC+1 schrieb > [email protected]: >> >> 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
