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 wrote:
> Windows is a great platform to work on. There are loa
Matt,
Thank you so much for your posting. My initial question was indeed
about both the webserver AND the database, but I believe you're the
first who commented on the latter.
I am already aware about the Django + MSSQL issue, but compared to the
Django+IIS, there are stable solutions that run sol
I notice that the conversation is mostly about IIS vs Apache.
You'll also want to think about the database. Django doesn't have
built in support for MSSQL. You could run Postgres or MySQL on
Windows, or there are some adapters for Django that will let it talk
to SQL Server. Either way, you'll prob
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 a
Ok, I see. Happily, this is not the case with us. We've discussed the
issue with the crew, and our decision is that most likely we'll deploy
on Win+Apache.
Hope there won't be any considerable development limitations due to
the use of the Windows Server OS.
Thank you a lot!
Regards,
Anthony
On D
On Fri, Dec 3, 2010 at 4:04 AM, ashdesigner wrote:
> 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 mea
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 Giral
On Thu, Dec 2, 2010 at 10:57 AM, ashdesigner 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 ju
Guys,
Again, the issue is just as follows:
1. Windows + IIS only(!).
2. Win/*nix + whatever else.
Our employed admins can administer IIS only. Which means, having to
deal with any other webserver (different from IIS) unbinds us from
using a Win platform at all.
Anthony
On Dec 2, 6:33 pm, Javie
Javier,
As a beginner, I don't have any own experience to judge, but browsing
through techy blogs I often saw FastCGI mentioned as someway 'slow',
'deprecated', 'IIS7-incompatible', etc. Maybe I am wrong, but using
PyISAPIe was described as 'much much faster'. You see, performance
matters signific
Lloyd,
Yes, correct. To us it is purely a webserver (IIS) issue.
Anthony
On Dec 2, 6:29 pm, Sithembewena Lloyd Dube wrote:
> True, Javier. But the issue isn't whether or not Django + Python can run
> smooth on Windows - it is a web server problem? Specifically IIS?
>
> On Thu, Dec 2, 2010 at 5:
Lloyd,
Yes, correct. It is purely a webserver (IIS) issue.
Anthony
On Dec 2, 6:29 pm, Sithembewena Lloyd Dube wrote:
> True, Javier. But the issue isn't whether or not Django + Python can run
> smooth on Windows - it is a web server problem? Specifically IIS?
>
> On Thu, Dec 2, 2010 at 5:25 PM,
On Thu, Dec 2, 2010 at 10:29 AM, Sithembewena Lloyd Dube
wrote:
> it is a web server problem? Specifically IIS?
if IIS can do FastCGI (and it should!) you can do django with flup
if IIS can proxy HTTP (and it would be weird if it doesnt), you can do
Django with gunicorn/tornado
or, you can ditc
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 wrote:
> On Thu, Dec 2, 2010 at 10:05 AM, ashdesigner
> wrote:
> > not to use Python/Django
> > +IIS+Windows because of lack of support and tools immatu
True, Javier. But the issue isn't whether or not Django + Python can run
smooth on Windows - it is a web server problem? Specifically IIS?
On Thu, Dec 2, 2010 at 5:25 PM, Javier Guerra Giraldez
wrote:
> On Thu, Dec 2, 2010 at 10:05 AM, ashdesigner
> wrote:
> > not to use Python/Django
> > +IIS+W
On Thu, Dec 2, 2010 at 10:05 AM, ashdesigner 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 Py
Correct :)
On Thu, Dec 2, 2010 at 5:05 PM, ashdesigner wrote:
> > I thank you all so much for the really valuable pieces of advice. All
> > in all, the underscore seems to be as follows: not to use Python/Django
> > +IIS+Windows because of lack of support and tools immaturity ("hack"
> > approach
I thank you all so much for the really valuable pieces of advice. All
in all, the underscore seems to be as follows: not to use Python/Django
+IIS+Windows because of lack of support and tools immaturity ("hack"
approach). One'd better deploy on Win/Unix + Apache, am I right?
On Dec 2, 5:39 pm, Jav
On Thu, Dec 2, 2010 at 9:22 AM, ashdesigner wrote:
> maybe I just don't get the point.
i guess the point is that nobody likes IIS, so there's no development
specific for that platform
--
Javier
--
Javier
--
You received this message because you are subscribed to the Google Groups
"Django
19 matches
Mail list logo
