🚀 go-pugleaf

"Joi Ellis [TeamB]" wrote:

> Alex Colic <alex.colic@pop-ware.com> wrote:
> > Ok, got the book looking at the examples.
>
> > Question: the apps that are doing the listening are a bunch of web apps
> > jsp/servlets. Lets say I have 5 of them and they all need to listen on this
> > port. If I create a monitor class that uses a ServerSocket than I can only
> > have one of these web apps listening.
>
> Hrm.  I thought Jsp/servlets run only when the web server is processing a page
> request.  You don't want to use jsp/servlets for this, I don't think.

I think the problem is with how Alex worded the description.  The servlets
would not, per se, "listen".  The ServerSocket would have to forward a
request to the appropriate servlet.  This is no different from JSP model 2
except that the delegation is being handled by the ServerSocket instead
of a central controlling servlet.  The complex portion is that servlets and
JSPs generally produce output, normally sent back along the HTTP
connection that the client originally opened.  Unless Alex is using HTTP
as the basis for that client-server interaction (in which case he wouldn't
need to bother creating a ServerSocket at all, just bind his JSP/servlet
container to the port), he'll need to create a specialization of servlet so
it knows about this socket and the protocol.  Not sure how you'd get
JSPs to work this way since I don't know if there is a way to control
which servlet class the JSP compiler will extend (definitely not something
I've tried to do before).