At 08:51 AM 11/27/01 -0800, 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?
Interesting question -- do you have the AppServer serve up HTTP directly, or do you have a separate Python process that accepts the HTTP request and forwards it using the standard Adapter format? Pros of using a single process: - it would be faster - it's easier to manage a single process rather than having to start up and monitor two processes Cons of using a single process: - you can't restart the appserver without potentially losing requests while it's restarting; with 2 separate processes the HTTP server process can hold onto the request and retry until the appserver has restarted - it makes the WebKit core more complicated since you're bundling in multiple protocols; by keeping the HTTP server process separate the core doesn't have to change at all Any others? -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
