Downloading Applications and Struts

[Michael McGrady]

A downloading application utilizing Struts, in my opinion, like the 
uploading applications, should have its basic classes somewhere else, 
like uploading is in commons.  Such an application, in my opinion, 
should merely present an interface that subclasses of Struts Actions 
can, directly or indirectly, reference.  Such an application, also in my 
opinion, should distinguish and decouple distinct behaviors as, for 
example, the distinction between the io functions and the management 
functions such as access control, choice between zip, folder and 
database sources, etc.  The demands of such applications, in my opinion, 
are too different from the purpose of the Action class to work well in 
the end in an Action class.  Shouldn't, for example, any cool solution 
for either downloading or uploading in the end be multithreaded?  Is 
getting or managing the receipt or sending of a file really within the 
proper scope of the Action class?

Michael McGrady
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]