Christian Boos wrote: > However, in TracOnWindowsIis6 [1] I currently read: > -- > Note 1: Before continuing to set up Trac to run using IIS6, > be warned that python running under IIS6 is painfully slow. > It is recommended that the use of tracd > <http://trac.edgewall.org/browser/trunk/README.tracd?rev=latest > be used for performance reasons. See > http://lazutkin.com/blog/2006/feb/18/setting-tools-windows/ > -> Section "Trac" -> Step 4. This results in a /significant/ > performance boost over CGI. > -- > > If I understood you correctly, your experience differs from this.
It's true that TracCgi is really slow on IIS. But as I'm working in a rather small development team I don't care about the performance. In my opinion it's also a bad idea to advise people to switch to tracd in any case. Many administrators have to follow corporate guidelines when setting up new software on their production servers. IMHO we (trac's IIS users) should start experimenting with some Python ISAPI filter and document the experiences in the wiki. Unfortunately, I did not yet have enough time to do so. Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
