hi raj,
Note: Servlet engine and container mean the same in this writing.
I need to correct my self little bit. It is the servlet engine proxy
that runs on a port. It is not the servlet engine that runs on a port.
Probably I need to make it more clear.
Take the case of Tomcat. Tomcat basically provides a web container. So
it contains a servlet container as well. Tomcat also has a web server
component. But Tomcat docs suggest that it is better for performance
reasons to use apache ( or any other web server) instead of the one
supplied with Tomcat it self.
When you configure Tomcat to work as a servlet engine on top of Apache,
Apache would be running on say 8000 while Tomcat Servlet Container proxy
would be running on say 8007.
Apache 8000--->Tomcat Servlet Engine Proxy 8007---> Tomcat Servlet
Container.
In the above situation, the Tomcat Servlet Engine proxy can only accept
requests coming from apache and not from a browser. Apache webs server
communicates with the proxy and not the Servlet Container.
is that okay !!
- Rao
> ----------
> From: Rajeshwar Rao.V[SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, May 15, 2001 5:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Reg: Servlets and ports
>
> Hi Rao,
> you mean both web server and servlet engine run on different ports.
> If that is the case, why cannt i access(or send request ) to servlet
> engine
> something like this:
> http://localhost:xxxx/
> where xxxx can be servlet engine port no.
> I think servlet engine does not run any port.it is web server runs on
> port.
> Please revert back ASAP with more comments.
> It seems to be interesting.
> -raj-
>
> -----Original Message-----
> From: Chalapathi Rao A L [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 15, 2001 4:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Reg: Servlets and ports
>
>
> The web server actually listens for the http requests on a specific
> port
> and if it finds that the request is made by a client for a servlet,
> the
> web server will forward the request to the servlet engine ( which is
> running on some port). The servlet engine executes the requested
> servlet
> and sends the results back to
> the client ( via the web server) .
> The web server and servlet engine are both required to run servlets.
> They are just two server processes running on different ports. But the
> clients can only directly send their request to the web server and not
> to servlet engine.
>
> hope that is clear.
>
> - Rao
>
> > ----------
> > From: Rajeshwar Rao.V[SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 15, 2001 4:49 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Reg: Servlets and ports
> >
> > Hi Nic,
> >
> > >servlet container does all the network stuff, such as listening to
> > the
> > port
> >
> > I have doubt now.Is it Servlet container or web server, which one
> > listens on
> > port?
> > As far as i know it is web server.
> > I think there is a big difference between web server and servlet
> > engine.
> > If i am wrong or want to add more stuff regarding this,please do it
> > ASAP.
> > regds
> > -raj-
> >
> > -----Original Message-----
> > From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 15, 2001 4:21 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Reg: Servlets and ports
> >
> >
> > >>> Raghavendran_c <[EMAIL PROTECTED]> 15-May-01 11:38:30 AM
> > >>>
> >
> > >Can servlets be configured to listen to any user-defined
> > >port or is it neccessary that they should listen to that port
> > >which the web server listens at ?
> >
> > Servlets don't really participate in the network environment. The
> > and dispatching requests to particular servlets.
> >
> > You probably don't understand the architecture, I suggest you read
> > some of the introductory material there is around:
> >
> > Resources:
> > http://java.sun.com/products/servlet/external-resources.html
> >
> >
> > >Can we develop mail server components using Servlets???
> >
> > No.
> >
> > See the archives:
> > http://archives.java.sun.com/archives/servlet-interest.html
> >
> >
> >
> > Nic Ferrier
> >
> >
> ______________________________________________________________________
> > _____
> > 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
> >
>
> ______________________________________________________________________
> _____
> 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
>
___________________________________________________________________________
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
