Search Results

All three properties are populated from different sources: req.query comes from query parameters in the URL such as http://foo.com/somePath?name=ted where req.query.name === "ted". req.params comes …

For reasons I can't quite explain, the push to stand-alone modularity in node.js seems to pull people away from creating common utility function that multiple modules can use. …

This really depends upon how many devices you're trying to support and how often a transaction occurs with a given device and how much data is involved for a given device. Based on that, reasonable so …

Yes, it is entirely possible. All you need at the core is the ability to have TCP server accepting inbound TCP connections in order to then implement your own HTTP server on top of that. The Net mo …

Rooms are a tool in socket.io servers for keeping track of groups of connected users. You can then iterate the sockets in a room or broadcast to all of them. There's really nothing more to them than …

If you are storing state on the server that is needed in order to process an incoming request from the client, then the server is stateful. Said another way, it has state that it stores and needs to …

Updates to shared state in a separate process are not immune to race conditions when you have multiple node.js processes all able to access it so you have to code shared state updates appropriately to …

In general, any function that does networking or uses timers to do things over a period of time will be asynchronous. If the function takes a callback, you can look at what the callback is used for …