🚀 go-pugleaf

Ok... here is the scenario:

I am launching a project site composed of a java application server and a
host of other tools not worth mentioning at this time.  My aim is to produce
java code that will allow a subscriber to download large files and if
needed, restart broken downloads.  Furthermore, I need to secure the entire
process by giving the subscriber a username and password all the while
keeping track of where the user left off in the download process... storing
the information in a database.  Such information is updated with each byte
being transfered.

The idea is that a subscriber will have access to a limited number of files
per month and such files may exceed 200 mb.  However, I dont want to break
up the files and certainly I dont want users downloading a portion of the
file and quiting out before the end to circumvent any sort of update to the
database.

Where should I start in terms of classes and which approach should I use?
Should I embed some technology into a java servlet (server side) and a java
applet (client side)?  Or can I also just use JSP to program the server
side?  Any suggestions?

Thanks


Steve Kothenbeutel
stevenkothenbeutel@hotmail.com