DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35089>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35089 ------- Additional Comments From [EMAIL PROTECTED] 2005-05-27 03:01 ------- Unless I as the consumer of the DownloadAction have the ability to control its destination (filename), I don't see how I can take advantage of the Action class. The end user does not want a file named MyDownloadAction.do. There may well be other use cases, but my present circumstance simply has the user requesting a particular file with the expectation of it arriving with the same name as the file the user requested. I had just completed writing my own DownloadAction when I discovered the 1.2.6/7 addition; as you might expect my code bears remarkable resemblance to the class being added to the standard offering. My version uses content-disposition (no surprise). I am arguing that the author of the DownloadAction subclass should have the option of specifying the content-disposition (or some other means of controlling the filename on receipt) within whatever limits the browsers pose. I believe that we are all headed in the same general direction... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
