Javier, Frankly, I just don't quite get the #3 option. Do you mean switching to *nix would entail considerable support/management issues? If so, why *nix - native to Django - as you say, could be a limitation to the framework? Is this what you mean?
Anthony On Dec 2, 7:23 pm, Javier Guerra Giraldez <jav...@guerrag.com> wrote: > On Thu, Dec 2, 2010 at 10:57 AM, ashdesigner <antony.shash...@gmail.com> > wrote: > > browsing through techy blogs I often saw FastCGI mentioned as someway > > 'slow', > > 'deprecated', > > you're reading the wrong blogs > > > 'IIS7-incompatible' > > that might be true, i have no idea. a big reason to stay far from IIS > > unfortunately, i've just checked that both Gunicorn and Tornado are > *nix only. no big surprise, since both use modern prefork+events > architectures, which are clumsy on windows (to say the least). > > so, i think you have few options: > > 1: find if IIS can do FastCGI (and it should) > > 2: switch to a complete webserver (apache, ligthttp, nginx) > > 3: switch platforms. > > in the long run, option 3 is the best; but dealing with management, > inertia and zealotry are huge obstacles, and it would be seen as a > Django limitation; so i would seriously try option 1 first. > > option 2 is very good also, and note that both ligthttp and nginx are > growing in usage precisely because they're extremely light and fast. > also, see the fact that both use FastCGI as the main method to connect > with backend apps. > > -- > Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
