Re: How do I force a 'Save Window?'
Dennis, Microsoft has documentation on how IE handles MIME types, content-disposition headers, etc. It may be out of date, and not accurate, but it's certainly worth reading. Have a look at: http://msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.as p There is also a support webcast with more information: http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc0111 01/wcblurb011101.asp In either document you'll see that application/octet-stream does not force a save window because IE classifies it as an ambiguous type. Note that you can always tell your users to right-click on the link and select Save Target As... to get a save window. Francisco [EMAIL PROTECTED] - Original Message - From: Dennis Daupert [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 7:10 AM Subject: Re: How do I force a 'Save Window?' Thanks all for the great suggestions. This group is wonderfully helpful. I tried the quick route, setting MIME type to application/octet-stream, and that works fine for xl spreadsheets, but I still get the same behavior as before with MS Project files (browser IE 5.00.3105.0106, which is one of the IE versions we have to support). I will need a bit more time to try some of the other more involved ideas , so that won't be for a few more days. /dennis -- - Office phone: 817-762-8304 -- - Great leaders never tell people how to do their jobs. Great leaders tell people what to do and establish a framework within which it must be done. Then they let people on the front lines, who know best, figure out how to get it done. ~ General H. Norman Schwarzkopf
Re: How do I force a 'Save Window?'
I clicked on the links I sent in my previous message and noticed that one of them didn't work because my mail program had split the url into two pieces at a line boundary. You may have to cut and paste the two pieces into your browser's URL box. You can also look for the documents by their titles in Google. The titles are Appendix A: MIME Type Detection in Internet Explorer and MIME Type Handling in Internet Explorer. Francisco [EMAIL PROTECTED] - Original Message - From: Francisco Corella [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Dennis Daupert [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 9:21 AM Subject: Re: How do I force a 'Save Window?' Dennis, Microsoft has documentation on how IE handles MIME types, content-disposition headers, etc. It may be out of date, and not accurate, but it's certainly worth reading. Have a look at: http://msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.as p There is also a support webcast with more information: http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc0111 01/wcblurb011101.asp In either document you'll see that application/octet-stream does not force a save window because IE classifies it as an ambiguous type. Note that you can always tell your users to right-click on the link and select Save Target As... to get a save window. Francisco [EMAIL PROTECTED] - Original Message - From: Dennis Daupert [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 7:10 AM Subject: Re: How do I force a 'Save Window?' Thanks all for the great suggestions. This group is wonderfully helpful. I tried the quick route, setting MIME type to application/octet-stream, and that works fine for xl spreadsheets, but I still get the same behavior as before with MS Project files (browser IE 5.00.3105.0106, which is one of the IE versions we have to support). I will need a bit more time to try some of the other more involved ideas , so that won't be for a few more days. /dennis -- - Office phone: 817-762-8304 -- - Great leaders never tell people how to do their jobs. Great leaders tell people what to do and establish a framework within which it must be done. Then they let people on the front lines, who know best, figure out how to get it done. ~ General H. Norman Schwarzkopf
Re: Documentation for Apache::exit()?
Hi Kyle, There are a few performance penalties when using Apache::Registry: * Scripts are compiled at first request instead of server start unless you use something like Apache::RegistryLoader. So, the first request per child will be a little bit slower and you don't get to share memory between httpd children. (Memory sharing can be a big problem.) * Every request runs through Apache::Registry::handler before your script gets called which has overhead including some setup code, an extra stat(), and a chdir(). (PerlRun and RegistryNG uses $r-finfo but Registry does an extra stat() -- not sure if there's a reason for that.) Thanks a lot. I hadn't thought of the memory problem. It seems that I'll have to bite the proverbial bullet and not use Apache::Registry. Francisco
Re: Documentation for Apache::exit()?
Hi Ged, Thanks for replying. I hope you had a good time in my old country :-) You probably saw the reports on the news about roads being washed away by the rain in Sevilla. I went on a motor-cycle. Camping. Mmm... Doesn't sound like the perfect vacation. I'm glad you made it back :-) If you're writing new code then I would recommend writing handlers and avoiding Apache::Registry altogether. Why do you recommend avoiding Apache::Registry? Apache::Registry is essentially just to get you going with mod_perl and your old CGI scripts. See for example mod_perl_traps.pod which deals with some of the 'gotchas' that you can run into. You can make better use of the Perl API using handlers. (Of course you might not need to.:) Is there a performance penalty for using it? Handlers can be faster, yes, but since you get such a big performance boost from mod_perl to begin with it's not usually serious. Read the the Eagle Book, the mod_perl Guide and the mod_perl CookBook. (That will take you most of the rest of the year...:) The details are on the mod_perl home page. Thanks for the pointers. I've read the Eagle Book already, and I check the Guide as needed, but I wasn't aware of the mod_perl CookBook. I've checked the table of contents on Amazon and ordered it. Francisco --- Francisco Corella [EMAIL PROTECTED]
Re: Documentation for Apache::exit()?
Hi Ged, Sorry it took a long time to reply. Been to Spain. Thanks for replying. I hope you had a good time in my old country :-) If you're writing new code then I would recommend writing handlers and avoiding Apache::Registry altogether. I had been thinking about whether to do this. Why do you recommend avoiding Apache::Registry? Is there a performance penalty for using it? Thanks, Francisco --- Francisco Corella [EMAIL PROTECTED]
Documentation for Apache::exit()?
Hello, The Modules book by Lincoln Stein and Doug MacEachern (pp.464-465) says that Apache::exit() can be used to halt script execution without terminating the process and without logging an error. The User Guide at http://perl.apache.org/docs/1.0/guide/index.htmlhas a section "Terminating requests and processes..." that alsodiscusses the need to use Apache::exit() instead of Perl's buit-in exit(). However, the Apache documentation itself does not mention an exit() function.Neither "perldoc Apache" nor the documentation at http://perl.apache.org/docs/1.0/api/Apache.htmlcontain the word "exit". Am I looking in the wrong place? Thanks, Francisco Corella [EMAIL PROTECTED]
