On Monday 26 November 2001 04:18 pm, Dan Wilder wrote: > Perhaps too much setup is required, with no GUI interface to > Apache's httpd.conf.
On Monday 26 November 2001 04:50 pm, Geoffrey Talvola wrote: > Apache works well on WinNT/2000 but it does require editing messy > config files by hand. �That's a big turn-off for many Windows people. But the original poster referred to installing the app on employee or customer laptops. httpd.conf is a text file which means writing a bit of Python code to whip it into shape for your custom app is doable and rather easy. In fact, I've done it for my own purposes. Also, one could add a handler to Python's own HTTPServer as is discussed in later messages. On Tuesday 27 November 2001 08:51 am, Mike Orr wrote: > Is there a reason Webware needs a socket connection between its > AppServer and a future built-in HTTP server? �Or could the HTTP > server just import the AppServer and run it on its own? �Would it > gain any performance advantagess? �Would there be any disadvantages, > besides not being portable to other HTTP servers? Having a separate web server means that restarting your app server is a delay for your users instead of an error message. In a production environment, that is fantastic. I would prefer a subclass of HTTPServer that communicates with WebKit and even launches it if it is configured to run locally. Then you would have all the conveniences including restarting and one command to launch. -Chuck _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
