I'm a little out of my element here so I'm really looking for some advice. I'm researching some options for running a OPeNDAP server. One option that looks pretty favorable for my current situation is http://pydap.org/server.html.
It is implemented as a WSGI application. Would NWSGI work with Pydap? Are there advantages/disadvantages of NWSGI vs isapi-wsgi (link below) with Pydap specifically? At this point Pydap is the only
python application I envision running on our Windows server in the near future.
Jan 4, 2011 at 10:11 PM
> Would NWSGI work with Pydap? Are there advantages/disadvantages of NWSGI vs
> isapi-wsgi (link below) with Pydap specifically? At this point Pydap is
> the only python application I envision running on our Windows server in the
> near future.
Whether NWSGI will work for you depends on whether Pydap works on
IronPython. I've never heard of it before (my first instinct was that
it was an LDAP server, which is a bit off the mark :), so I don't know
how well it will work. Unless Pydap works out of the box on
IronPython, or you've got the time to troubleshoot Pydap under
IronPython and file bugs (which would be awesome and much
appreciated), you're probably better off using CPython and isapi-wsgi.
If Pydap does work under IronPython, then NWSGI will (in my completely
unbiased, I assure you, opinion) easier to configure and manage, as
you can use the IIS management console to change all of the settings.
Performance should be about equal in either case.