How about renaming the current HTTPPort to AdapterPort, i.e:
HTTPPort = If EnableHTTP is True, then the built-in web server listens to this port for web requests.
AdapterPort = If EnableAdapter is True, then the application server listens on this port for requests from the mod_webkit adapter.
An unfortunate side effect of this would be confusion with old config scripts.
-winston
On Dec 1, 2004, at 5:01 PM, Jason Hildebrand wrote:
On Wed, 2004-12-01 at 15:38 -0600, Ian Bicking wrote:I think I prefer the name 'BuiltinHTTPServerPort' over 'HTTPPort' though.
It's annoying long, but 'HTTPPort' is very likely to confuse new webware
uses who haven't yet grasped how a webserver and the appserver typically
communicate. I foresee someone setting up apache on port 80, and then
also setting 'HTTPPort' in Webware to 80. :(
This confusion is a problem, but maybe it would be preferable to put in
a better error message when we try (and fail) to bind to a socket?
BuiltinHTTPServerPort is just a little on the long/hard-to-read side.
If we could reliably do this, I'd be tempted to propose:
try:
sock.bind(serverAddress)
except:
print 'RTFM!'
os.system('xloadimage %s/WebKit/Docs/arch.gif' % self.webwarePath())
But seriously, your idea (of providing helpful feedback to the user) is a good one.
I'd (personally) be happier with EnableHTTP too.
peace, Jason
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
