Why are you reading data from the response object and not from the request object #982
|
In this example you are reading the data from the response object. Shouldn't the data be read from the request object? Usually, the user makes a request from the client to the server and that request contains the data. Then, the server reads that data from the request. After that, the server does some work and uses the response object to send data back to the client. Ins't it the case here too? |
Answered by
uNetworkingAB
Oct 27, 2023
Replies: 3 comments 1 reply
|
Then it’s even more strange, if |
0 replies
|
Honestly, it's splitting hairs. Consider it a quirk kept for backwards compatibility. |
0 replies
Answer selected by
uNetworkingAB
|
We read data from request to prépare tje response. Literal wtf
Le sam. 28 oct. 2023, 01:06, uNetworkingAB ***@***.***> a
écrit :
… Honestly, it's splitting hairs. Consider it a quirk kept for backwards
compatibility.
—
Reply to this email directly, view it on GitHub
<#982 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIUGDOFCMWGFV2EX3UNDBC3YBQ5ABAVCNFSM6AAAAAA6TGDS5WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TIMBYGEYTQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: <uNetworking/uWebSockets.js/repo-discussions/982/comments/7408118@
github.com>
|
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Honestly, it's splitting hairs. Consider it a quirk kept for backwards compatibility.