>One question I have is how to determine which ports are available
>if there is no global list of available ports in the filesystem.
>Maybe this is straightforward socket code -- I'll have to experiment a bit.
Seems like this would have to be configurable. The admin might want to
setup a range of valid ports, like 9000-9050, so as to not interfere with
other known apps. You could go through the ports round robin fashion, but
be careful not to use one still be used by a dying app server.
Since starting a new app server is a rare event, reading a config file for
it is no big deal.
>Also, I may need file locking or a mutex around the reading and writing
>of address.text to avoid having multiple simultaneous CGI adaptor requests
>start up multiple appservers.
Regarding your earlier comment about performance on Windows, if that's an
issue for you, were you leaning towards:
a. C adapter code base
b. lightweight adapters and a middle, dispatcher process in Python
c. ack! heavyweight adapters in both C and Python that duplicate
each other's functionality.
Chuck Esterbrook wrote:
> Regarding your earlier comment about performance on Windows, if that's an
> issue for you, were you leaning towards:
> a. C adapter code base
> b. lightweight adapters and a middle, dispatcher process in Python
> c. ack! heavyweight adapters in both C and Python that duplicate
> each other's functionality.
I was actually leaning toward option c. But I'm much more concerned with
reliability than with speed at this point -- the application I have in mind is
relatively low volume, but may have pages that are somewhat computationally
expensive. So I can live just fine with a Python CGI adaptor for quite a while.
It may also be possible to use Python/COM to create an efficient interface to
IIS in pure Python. I'll look into that at some point.
- Geoff Talvola