I'm in the process of making a Java application with a corresponding update application. At any given time the user may want to update the application and the updater will ask for a list of files of the latest release. Based on this list, the updater can determine which files need to be downloaded to complete the update.

I now have 2 approaches to solve this, but i would like to know what approach will put the least stress on my application and server.

1. I could send a list of files i want to download to my server and the server zips the files and simply returns this compressed file to the application.

2. The updater sents a request for each seperate file to the server, which simply returns the file

The application will be used mainly in Belgium and The Netherlands and connections/bandwidth tend to be pretty decent in here.
The average size of a single file should be around 100Kb and at most 1Mb.
I expect an update to have anywhere between 10 to 50 new files.
I expect at most 100 persons/day to update the application, i.e. in the week when a new version is released.

I hope this is enough information to sketch my problem and any advice is welcome. If there is another common way to tackle this, i'd be glad to hear it.