Return-Path: <ronald.haring@siennax.com>
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 67895 invoked from network); 19 Jul 2000 10:50:52 -0000
Received: from unknown (HELO mail.ilcampo.com) (193.172.126.1)
  by locus.apache.org with SMTP; 19 Jul 2000 10:50:52 -0000
Received: from roha ([213.35.44.113]) by mail.ilcampo.com
          (Netscape Messaging Server 4.1) with ESMTP id FXXY4000.E0W for
          <tomcat-dev@jakarta.apache.org>; Wed, 19 Jul 2000 12:50:24 +0200
Message-ID: <002f01bff16e$a899c6d0$3400a8c0@roha>
From: "Ronald Haring" <ronald.haring@siennax.com>
To: <tomcat-dev@jakarta.apache.org>
References: <008b01bff096$9d5383c0$3400a8c0@roha>
 <3974A6F9.2564F2C@eng.sun.com>
Subject: Re: inner workings of servletContext
Date: Wed, 19 Jul 2000 12:46:56 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

thanks Craig and Costin for your answers. I found out meanwhile that my
knowledge is lacking in the requestinterceptor area, so anymore insight will
be appreciated.

Gr
Ronald
--------------------------------------------
If at first you don't succeed, skydiving is not for you.

----- Original Message -----
From: "Costin Manolache" <costin@eng.sun.com>
To: <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, July 18, 2000 8:50 PM
Subject: Re: inner workings of servletContext


> Ronald Haring wrote:
>
> > Hi all,
> >
> > I'm looking for some information on the inner workings of the tomcat
> > webserver and java web servers in general because I want to make a
server
> > log-on procedure using tomcat. I'm trying to step and trace thru the
code
> > (using System.out.println (sigh)) and I think I've got the general
picture
> > but I would like to test my knowledge against some more reliable papers
than
> > my own.
> >
> > Can anyone point me in the right direction or have any hints?
>
> Most web servers work in the same way - after the request is parsed
> the modules ( Interceptors in tomcat, Filters in IIS, SAF in NES,
> hooks in Apache 2.0) have control and decide if the request is
> authorized or not.
>
> If it is, everything goes on and the request is processed.
>
> If the request is not ok ( wrong or no credentials ) the module will
> return a 500.
>
> The server will then handle the 500 and call a handler ( for tomcat
> the module can also modify the handler, that's true for most
> other servers).
>
> Costin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>