Is it atomic for Http to request api to get data?

for example, if you call an api interface with httpclient and the payload returned by the API at one time is 5MB, then the data received by the httpclient in one call
1) Atomic: either the 5MB receives all of the data, or the underlying layer only receives some of the data, and throws an exception when it times out before receiving all the data.
2) non-atomic, you can only receive part of the data to the caller

.

what happens?

Dec.23,2021

will finish receiving, otherwise an error will be reported. But it should not be called atomicity, and there are countless operations in between. Maybe the integrity is better.


what was said upstairs is true. In addition, when receiving the data, the underlying layer is processed by the transmission protocol, and when the server sends the data, the data will be subpackaged and framed, in order to improve the transmission efficiency.
when the client receives data, the protocol also reassembles the received data frames into complete data, including operations such as data verification.
it can only be used after the data has been received.
is generally transmitted using the TCP protocol. If the data is missing due to packet loss or other circumstances, the server will reissue the data (this is uncertain).
may be that the server sends multiple messages as soon as it starts, or the client requests a reissue.

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1e55c19-5a3a5.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1e55c19-5a3a5.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?