Date: 2004-01-27T14:04:43 Editor: 203.45.72.167 <> Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer
no comment Change Log: ------------------------------------------------------------------------------ @@ -5,7 +5,8 @@ The implementation of the Geronimo web tier will be guided by the use cases outlined below. It is the intent of this project to meet these use-cases without resorting to implementation specific -configuration. +configuration. Specifically, these are actions that typical geronimo users are likely to perform and should be able to be documented, supported and managed as geronimo actions, rather than anything +specific to the underlying implementation of the web container. = Use Cases = @@ -46,7 +47,11 @@ The deployment of a web app may be targetted deploy against a specific subset of web connectors, so that it will be available only on specific physical interfaces, ports, protocols etc. Typically this will be to allow additional network security to be applied to administration -and/or web services interfaces. +and/or web services interfaces. + +For good default security, the default geronimo configuration should start administrative +interfaces such as the jmx console are only available on localhost and on a port that is +distinct from the default web application deployment. == Web Component Dependencies == @@ -64,6 +69,13 @@ some web infrastructure (connectors, SOAP servlet) may need to be initialized, perhaps dynamically. Ideally this will not be within the default web container, as this is unlikely to have desirable default security implications. + +== Run states == + +Management of a cluster may need additional run states than those defined in JSR77. Gentle shutdown of +nodes may required modes where no new requests/connections/sessions are accepted by a node, while +existing requests/connections/sessions are allowed to complete. These modes may need to be applied +to web connectors and/or webapplications. = Architecture =
