> You perhaps don't understand WSGI if you thing you are bound to using
> Apache if you start using mod_wsgi. The mod_wsgi module is just one

i think i fully understand this one point. my application is intended
to be delivered "web 3.0" (doh!) style---server and client may be
deployed to any machines that can see each other over HTTP. a minimal
installation can of course take place on a single machine.
furthermore, installation for the client should be zero (i.e. a
classical web-application), and installation for the server
(optionally) *close* to zero (currently you need to install python 2.5
plus a number of packages such as werkzeug). i have chosen sqlite over
mysql for the database so customers are not obliged to explicitly
install a database. (also, the targetted browsers are only firefox and
safari, which makes web development almost feel like a walking down
the beach on a sunny day. early on i decided against POW and gears, as
that would tie me to firefox.)

as long as the server serves one or few clients, even wsgiref has been
powerful enough so far to satisfy demands. it has the advantage of
running right out of the box. i will try to get the cherrypy server
running, too---it's just one medium sized file, and if it's faster
than wsgiref, all the better.

the last time i set up nginx (on windows, omg), installation and
configuration was a breeze. i have installed and configured apache so
many times and always wished it had been nearly as simple as with
nginx. i also like the way nginx communicates with web applications:
you run your application server(s) with whatever can publish content
on high ports (such as 5000, 5001, ...) and tell ngninx to listen
there and mirror to port 80. the beauty of this is that your
application server and the front server remain decoupled to a high
degree. development and production setup are nearly identical. when i
last used mod_python, i never got rid of the feeling that the inner
workings of it were not fully transparent to me. maybe mod_wsgi is
better in this respect. but for now, the preferred installation for a
customer that wants to serve more than a few clients is using nginx. i
do not have performance statistics at hand, though. it just looked
fine.

cheers & ~flow





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pocoo-libs" 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/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to