Welcome, my friends.
Welcome to the stiction.
In this section, we will learn about the subject and what all concepts we need to learn revolving around
the subject container, the container basically is your Puncak Web server, which we are going to use,
and it hosts the Soviet or the GSB.
The GSB is just another way of saying that it is a solitary.
So a GSB gets translated into a servlet and that job is also done by the servlet container.
We learn about it in some other course on GSB.
In this course we will be focusing on the Soviet, the Soviet container or the Soviet.
So what can it do?
So what exactly does a solid container do, what other things?
It performs many functions.
First of all, it manages the life cycle of the sonic.
It not only hosts the Sonic, but also manages the entire lifecycle of the subject.
It takes a request from the client.
The client can be a browser and takes those requests.
So basically a solid container works as it's also a Web server.
We have talked about Web server, Tomcat Web server.
So it takes requests.
It sends back a response to the client.
It could be in the form of e-mail or text.
Right.
And then it manages might be trading of the server.
We learn about this a little later.
More about this a little later in some other section.
But market trading as such is an ability to do to multitask, to create multiple processors simultaneously.
It gives the illusion that many things are happening at once.
So that's what multitracking simply means.
And it manages this.
The strong web server manages doing that for the subject.
And finally, it translates as GSP to a server and runs it on the server.
So as I have already told you before, that a GSP is essentially a like a GSP gets converted into a
server and this job is done by Omkara to stand by the server container and it runs also.
That's Soulik automatically it runs that subnet on the server.
So you don't know about it that actually a Jaspin GSP has been converted into Soulet.
It's happening in the background.
We'll just see how that happens when we go to GSB later.
We are focused on subnets as of now.
Callback mechanism.
So what is a callback mechanism for to.
This is a very important concept as far as servlet container is concerned, servlet containers make
a call back to the subject program that you create.
What does that mean?
That means that.
He calls your method the support of the servlet container, called the method that you create nobody
else.
You don't call the method.
It is the of container, it is the Tomcat lipservice that calls the.
That calls the matter on your servlet.
So who calls whom?
Yes, and who was the control?
The control is with the Tomcat, so and the Bangkok Observer calls the method.
These are set methods like like the Post, like get like destroy.
These are standard methods which have to be sensitively written and exactly in the same boat as to be
written with the same signature Java signature.
And they will be called by the Tomcats from Carib.
So that is the main method.
There is no mean method indeed.
So yes, that's a fact.
The servlet doesn't contain any mean main method, but in the Java program, we understand and we know
that the starting point is always the main method.
So that is the meaning.
The mean method is in the contact, which some men in the top over the main method is there.
So the server runs, the mean method runs, and it makes a callback.
It makes a call to your method.
So the main method exists in the.
Tom Catchlove, as I have already told you, the Tomcat server has the control Life-cycle Manhood's
standard method scored by the server on your court, as I have already told you before, that life-cycle
methods are present in the in your servlet, which you create.
These methods are guarded by the Tomcat.
So these are standard methods.
They have a particular syntax, but a particular semantic bit of writing it.
And you will learn that what that method is and it will be guarded by the server when the lifecycle
method one by one after one, like, for example, first you will call the service method.
Then it called the Save the gate method.
Then it might call the destroy method.
So there are certain ways in which these things look and we will discuss about this in the later.
Next, we will see the lifecycle of assembling the lifecycle methods I'm talking about.
We will now go through the lifecycle.
What does my lifecycle methods are and in what order do they happen?
We will see that in the next lecture.
Thank you very much.