How to receive a file using sendfile?

send a file with sendfile is easy:

stat(fd,&filestat);
sendfile(sockfd,fd,0,filestat.len)

but how to receive a file using sendfile? since I don’t know the length of the file, should I send the file length first?

 sendfile(fd, sockfd,0, ??)

There seems to be two ways of doing this:

1. send the filestat.len first

   //send end
   write(sockfd,filestat.len);
   sendfile(sockfd,fd,&offset,filestat.len);
   //receive end
   read(sockfd,&len);
   sendfile(fd,sockfd,&offset,len)
   

2. use a loop in the receive end:

   //receive end
   while(sendfile(fd,sockfd,&offset,BUF_LEN) > 0) {
       offset += BUF_LEN;
   }
   

Which one is better? Should I handle the buffer length specifically? Is there any problem in the first way when the file is quite large?

(I really like the mac os version of sendfile, it will send till the end of file if count is 0)

Answer

This is a great question!

The other posters are correct: you could call read() or recv() (what is the difference?) repeatedly until either of those returns 0, which indicates end of file (EOF).

However! You should consider first passing the size of the file, as a good practice. This would allow your client to anticipate exactly how much data is coming through the socket, figure out if (for example) there is enough disk space, etc. It allows you to have some sort of sanity-checking before committing to downloading whatever the server tries to send.

(This has its own perils. What if the server sends the wrong size?)

You might also consider sending the file in chunks. This way, if there is an interruption, you have a greater granularity when figuring out how much you’ve transferred. (The kernel does this for you anyway. But food for thought.)

Sending a single integer (a file size) over the network isn’t too difficult, but there are a few tricks to be aware of if you are very worried about portability.

Good luck!