The same bugs I found on Windows/Apache, also occurred on Linux/Apache. Until v5, I would stick with IIS 5. Also, as far as performance goes, I did bench testing on all of these platforms. I found that on the same hardware, there is no significant difference between Linux/apache, and windows/apache. There is a small performance increase with apache over IIS, but this is negated with the ease of use of IIS. Also, the bottleneck is Tango, not the webserver. Tango v4 has no support for keepalive, and poor threading, which makes it the dog. Whether you use Linux,windows 2000, or apache, netscape, or IIS, the performance is basically the same.
-- Robert Garcia BigHead Technology 21053 Devonshire Suite 206 Chatsworth, Ca 91311 Phone 818.773.8162 Fax 818.773.8164 http://www.bighead.net/ [EMAIL PROTECTED] > From: "Scott Cadillac" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Wed, 5 Jun 2002 09:13:30 -0700 > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > Subject: Re: Witango-Talk: HTTP Header Content-Disposition: Problem[must > read] > > Thank you Robert, > > This is a very useful piece of information. I often have my own debates as > to whether to switch back to Apache on Windows - but you've answered this > for me. Secure document management is an important piece of my application - > thank you. > > Does anyone have some feedback about Witango on Linux/Apache over > Windows/IIS (this is a performance and stability question - not security)? > > This has come up for discussion again lately, with us internally. Are there > now any better ODBC solutions available on Linux these days? > > Just speculating. Cheers.... > > Scott Cadillac > http://xml-extra.net > [EMAIL PROTECTED] > > VP, Research and Development > Plus International Corp. > 604-460-1843 > [EMAIL PROTECTED] > http://www.plusinternational.com > > Vancouver, BC, Canada > > Does your company have an Enterprise Information Portal? Check out Salsa at > www.plusinternational.com/flash/salsa.htm > > ----- Original Message ----- > From: "Robert Garcia" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> > Sent: Wednesday, June 05, 2002 8:50 AM > Subject: Re: Witango-Talk: HTTP Header Content-Disposition: Problem[must > read] > > >> I had major problems using content disposition with Apache, although I > have >> not used SuiteSpot. I have found that serving binary information from > Tango, >> and messing with HTTP headers works well with Tango/WebStar, and also > works >> well with Windows/Iis 5.0. It DOES NOT work correctly on Apache. After >> spending some time with Phil and Andre about this, they are going to work > to >> fix these issues with v5. >> >> My recommendation to you and anyone else using anything other than IIS > with >> Tango 4, is to switch to IIS 5. Tango just seems to work much better in > that >> environment. I lost a couple of weeks of my life dealing with these > issues. >> They all went away when I went to IIS. >> >> -- >> >> Robert Garcia >> BigHead Technology >> 21053 Devonshire Suite 206 >> Chatsworth, Ca 91311 >> Phone 818.773.8162 >> Fax 818.773.8164 >> http://www.bighead.net/ >> [EMAIL PROTECTED] >> >>> >>> From: Hutch White <[EMAIL PROTECTED]> >>> Reply-To: [EMAIL PROTECTED] >>> Date: Wed, 5 Jun 2002 08:28:38 -0500 >>> To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> >>> Subject: RE: Witango-Talk: HTTP Header Content-Disposition: Problem >>> >> >>> I'm using Netscape Suitespot on a Windows 2000 platform. I'm still > messing >>> around with the HTTP header content type and content disposition values. >>> That's the problem with this business, I keep having to learn stuff ;-) > I >>> read a security bulletin the IE 6 when it evaluates a file for security > goes >>> off the content information, but when it actually processes the file, it > takes >>> a look at the actual content and goes from there. They were saying that > was a >>> problem as you could name an exe file a .txt file and it would pass > security, >>> but when the download took place, IE 6 would run the exe file. That > looks >>> like what's going on here. I think I will need to actually build the > taf, >>> create fhe file object on the fly with real tab delimited data and go > from >>> there. Thanks for the help and I'll probably be back asking questions > once I >>> get this thing built up a little. >>> >>> Hutch >>>> -----Original Message----- >>>> From: Robert Garcia [mailto:[EMAIL PROTECTED]] >>>> Sent: Wednesday, June 05, 2002 3:03 AM >>>> To: Multiple recipients of list witango-talk >>>> Subject: Re: Witango-Talk: HTTP Header Content-Disposition: Problem >>>> >>>> Which webServer are you using, and what platform? >>>> >>>> -- >>>> >>>> Robert Garcia >>>> BigHead Technology >>>> 21053 Devonshire Suite 206 >>>> Chatsworth, Ca 91311 >>>> Phone 818.773.8162 >>>> Fax 818.773.8164 >>>> http://www.bighead.net/ >>>> [EMAIL PROTECTED] >>>> >>>>> >>>>> From: Hutch White <[EMAIL PROTECTED]> >>>>> Reply-To: [EMAIL PROTECTED] >>>>> Date: Tue, 4 Jun 2002 14:23:48 -0500 >>>>> To: Multiple recipients of list witango-talk > <[EMAIL PROTECTED]> >>>>> Subject: Witango-Talk: HTTP Header Content-Disposition: Problem >>>>> >>>> >>>>> I need to allow the user to download a tab delimited file. I need to > force >>>>> a download of the txt file and IE 6.0 insists on displaying the file. > When >>>>> I use the >>>>> Content-Disposition:attachment in the http header, it still goes to > the >>>>> screen. Any suggestion? >>>>> >>>>> Thanks in advance. >>>>> >>>>> Hutch White >>>>> IT Development Specialist >>>>> Capital Pacific Holdings, Inc. >>>>> 1717 W. 6th St., Ste. 140 >>>>> Austin, TX 78703 >>>>> Phone : (512)320-8888 >>>>> Mobile: (512)750-3346 >>>>> FAX : (512)320-0724 >>>>> EMAIL : [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>> >>> >> >> >> > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
