Consider two pseudo$-$code snippets illustrating file transfer mechanisms between a client and a server.

Pseudo$-$code $1$: Client:

file $=$ openFile$("$localFile$.$txt$")$ chunk $=$ readFileChunk$($file$)$ while $($chunk is not empty$)$ transmitData$($chunk$)$ chunk $=$ readFileChunk$($file$)$ endWhile closeFile$($file$)$

Server:

file $=$ createFile$("$receivedFile$.$txt$")$ while $($dataAvailable$())$ chunk $=$ receiveData$()$ writeFileChunk$($file$,$ chunk$)$ endWhile closeFile$($file$)$

Pseudo code $2$: Client:

file $=$ openFile$("$localFile$.$txt$")$ data $=$ readEntireFile$($file$)$ transmitData$($data$)$ closeFile$($file$)$

Server:

data $=$ receiveDataUntilComplete$()$ file $=$ createFile$("$receivedFileComplete$.$txt$")$ writeEntireFile$($file$,$ data$)$ closeFile$($file$)$

Which of the following statement$($s$)$ are true?

Pseudo$-$code $1$ demonstrates a chunked data transfer mechanism, suggesting that the data is transferred in parts, which might be beneficial in case of large files or unstable network connections.

Pseudo$-$code $2$ illustrates a file transfer mechanism where the client reads the entire file into memory before transmission, which might be more efficient for smaller files but can be problematic for very large files.

Pseudo$-$code $1$ relies on a connectionless data transfer model, given that there's no explicit connection establishment or termination.

Pseudo$-$code $2$ suggests that the server has a mechanism to detect when the data transmission is complete, indicating the need for some underlying protocol or metadata to signal the end of transmission.