Re: [Webware-devel] socker error handling bug?

[Christoph Z. <ci...@on...>]

Am 23.05.2019 um 11:26 schrieb Kerrison, Adam:
 > Our setup is Browser -> AWS ELB -> nginx load balancer (container in 
kubernetes) -> webware (container in kubernetes)

Ok, so you're using the built-in HTTP server (EnableHTTP=True)? Because 
the appserver by default cannot be directly used from the browser.

Note that the built-in HTTP server (i.e. running the ThreadedAppServer 
with HTTPAppServerHandler) is actually not a recommended solution for 
running in production under heavy load since the HTTPAppServerHandler is 
based on the standard lib's BaseHTTPServer.

We are currently thinking about the next Py 3 compatible version of 
Webware. Are you interested in that as well?

My plan is to just provide WSGI so that you can use any WSGI compliant 
server to serve Webware apps, and remove all the old server related 
components and adapters from Webware.

This will also allow running Webware with multiprocessing.

Btw, may I ask whether you use Webware Sessions and which variant? 
Because if you're using several Webware processes with load balancing, 
the default Memory/Dynamic session stores don't work. We will also need 
a new default Session system when supporting multiprocessing.

-- Christoph