We use a similar approach in our report system. Actually we have a
dispatcher servlets, which redirects requests to specialized servlets. All
of them aren't HTTP servlet, because we create own version of a request and
a response. Many console applications can be consider as servlets. I think
the advantage of such approach is a creation plugable components with static
interface.
Dmitry.
----- Original Message -----
From: Sullivan, Sean <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 03, 1999 6:14 PM
Subject: custom (non-HTTP) servlets, subclassing GenericServlet
> Has anybody built their own custom (non-HTTP) servlets?
>
> It appears that the way to go is to subclass GenericServlet.
>
> What are the advantages of this approach?
>
> Are there real world examples of this being done (other than HTTPServlet)?
>
> Thanks.
>
> -Sean
>
> ________________________________
> Sean C. Sullivan
> Senior Software Engineer, Intel Corp.
> [EMAIL PROTECTED]
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
