What will happen if some value returned from 'request' event handler?

Hi, I have a question in Mock Services (1), I noticed that the mock service used several return void res.end()
.void res.end()
will discard the return value of res.end()
which is res
itself. Then it will replace it with undefined
.
As far as I observed, the purpose is to interrupt the process of the handler function of 'request' event. So my question is: what will happen if the handler function returns some value other than undefined?
Best regards.
Answers
-
hey @krave good question, thanks for asking it I was hoping to be asked one day, it's sort of like you've found the easter egg
🥚.
So here's what it is, if you're writing a barebones http server you're going for something quick and cheap or you're going for performance engineering and
return void res.end()
caters to both of those things. Generally speaking JavaScript makes the developers life easier. At least in the sense that it is low-ceremony, low friction (importantly: at low scale). In limited scenarios where performance is considered a (genuine) business priority I use a different set of habitual coding practices. In the course material performance isn't stated as a priority, because it isn't but I left it there as a breadcrumb for discussion on this topic.One of the typical underlying JS engine optimizations revolves around object shapes, as in what properties does it have, what are the types (primitives or nested object shapes - which, in the engine layer are kind of the same) and so on. If the object-shapes (or primitives) that you pass to a function AND the shapes/prims you return from a function are consistently the same then you have a monomorphic function. JS engines can optimize monomorphic functions because they have reliable "types". One you return a different shape, or input a different shape into the function, now it's polymorphic. JS engines can optimize for that as well, up to a limit, there's only so many different shapes you can input/return from a JS function before it becomes megamorphic. Last I checked it was 4 (in V8), but it could change and be different in different JS engines. Megamorphic will be the slowest executing.
Ok so why
return void res.end()
it's just short hand for:res.end() return
The only point being made is to consistently return the same type. BUT
return void res.end()
sticks out and that is on purpose, it make it obvious that this function should always returnundefined
. Whereas the conventional way, is more familiar and implicit. To reiterate, this is not a practice I'd recommend for general usage. It's part of a different rule set.So, there is NO PROGRAMATIC EFFECT to returning something else from the listener function, it doesn't do anything with the return value. However, if you're in a position where you're setting out to use practices that mitigate the death-by-a-thousand-cuts style dispersed bottleneck problems ahead of time then it's important to consider there IS A PERFORMANCE EFFECT.
It's a little dated now but the general concepts still apply: I wrote a post about JS performance, this links straight to the section on polymorphism:
Appreciate the question @krave ✌️
0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2.1K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 158 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 25 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 37 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 18 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 236 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 538 Off Topic
- 131 Introductions
- 217 Small Talk
- 22 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 61 All In Program
- 61 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)