Pete,
Thank you for your advice, and considering our rather long discussion
I already think now that Win+Apache+MSSQL is the best way out for us
indeed. Both for performance and support matters.
Anthony
On Dec 3, 4:57 pm, CrabbyPete <pete.do...@gmail.com> wrote:
> Windows is a great platform to work on. There are loads of tools and
> support for Windows. The issue is not Windows vs Linux
> the issue is Apache ( which works great on Windows ) v IIS. If your
> admin is wants to use Windows by all means stick with it, and just
> install Apache. I developed on Windows and deployed on both Windows
> servers and Unix servers. Stay platform neutral and it won't matter.
>
> On Dec 2, 10:32 am, ashdesigner <antony.shash...@gmail.com> wrote:
>
> > Javier,
>
> > Under "hack approach" I meant PyISAPIe + IIS (wich is weird by itself,
> > but still).
>
> > Anthony
>
> > On Dec 2, 6:25 pm, Javier Guerra Giraldez <jav...@guerrag.com> wrote:
>
> > > On Thu, Dec 2, 2010 at 10:05 AM, ashdesigner <antony.shash...@gmail.com>
> > > wrote:
> > > > not to use Python/Django
> > > > +IIS+Windows because of lack of support and tools immaturity ("hack"
> > > > approach).
>
> > > not at all. there are lots of goods reasons to go the *nix route (be
> > > it Linux, BSD, Solaris, etc). but Django does work anywhere Python
> > > does.
>
> > > FastCGI is _not_ a 'hack'. It's a standard
>
> > > --
> > > 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.
