Let's see, I missed most of the latter part of this discussion. I'll add to the Wiki pages, but there's a particular point I was confused about:
On Wed, 2001-11-21 at 14:13, Tavis Rudd wrote: > * At what stage in the request-response cycle does authentification > take place (Adapter, Application, or Servlet)? > Doing it at the Adapter level means we can use the same mechanism to > protect content that isn't served via WebKit. Doing it at the > Application level means that we can also protect static content that > is served via WebKit. Doing it at the Servlet level means that we can > only protect servlets. I'm not entirely clear about what you are thinking of here. First, isn't everything Webware serves a Servlet? Even static files (that are handled by Webware) are passed through as a servlet. Also, what would it mean to have authentication at the adapter level? That seems identical to the Application level, more or less... anything that goes to the adapter goes to the AppServer, which goes to Application, which will almost certainly go to some ServletFactory and then a Servlet, no? For non-Webware resources, you'd have to do something else entirely. The adapters don't seem to relate. Ian _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
