1
00:00:00,780 --> 00:00:01,290
Welcome my.

2
00:00:01,740 --> 00:00:08,550
Welcome to this lecture in this lecture about attributes in the previous lectures we had gone through

3
00:00:08,580 --> 00:00:10,930
in bottoms as well as barometer's.

4
00:00:10,950 --> 00:00:12,630
Now we will go through attributes.

5
00:00:12,990 --> 00:00:17,490
Attributes are basically objects as opposed to parameters being string's.

6
00:00:17,490 --> 00:00:20,000
The type of parameter is always adjusting.

7
00:00:20,160 --> 00:00:26,760
The shape of an attribute can be any object that can be read and written, as opposed to parameters

8
00:00:26,760 --> 00:00:28,590
which can only be read in it.

9
00:00:28,590 --> 00:00:34,560
But mean does can be only read, but attributes can be read and write particular also.

10
00:00:34,710 --> 00:00:36,150
And they can also be removed.

11
00:00:36,810 --> 00:00:40,680
They can be in three scopes which are in the next slide.

12
00:00:40,680 --> 00:00:44,520
In the next slate, the three scopes of attributes should be covered.

13
00:00:45,450 --> 00:00:51,390
So attribute scopes, the first scope of an activity, the smallest, the most narrower scope is the

14
00:00:51,390 --> 00:00:52,280
request scope.

15
00:00:52,980 --> 00:00:55,490
OK, and you get this from the request object.

16
00:00:55,980 --> 00:00:59,660
The methods are set out to be able to get that attribute and remove it to do.

17
00:01:00,030 --> 00:01:02,640
You said the act of using the same method.

18
00:01:02,640 --> 00:01:09,040
You get an attribute for using the method and you remove the attribute if you want to believe that OK

19
00:01:09,120 --> 00:01:10,220
from the request object.

20
00:01:10,380 --> 00:01:12,330
So the first scope is the request.

21
00:01:12,720 --> 00:01:18,500
The second scope is the application scope, which again has the same methods so that you get that you're

22
00:01:18,510 --> 00:01:19,500
going to move back to attribute.

23
00:01:19,860 --> 00:01:25,410
And it has got from the public on fixed object from a subject context object.

24
00:01:25,410 --> 00:01:33,390
If you if you get the scope applique, you get an application wide scope for the attributes.

25
00:01:33,570 --> 00:01:36,300
These attributes can be shared between subnets.

26
00:01:36,660 --> 00:01:41,260
So also let's sort of share this attribute within an application.

27
00:01:41,440 --> 00:01:48,330
OK, extracted it will be an attribute only in the scope of that request that has been passed.

28
00:01:48,630 --> 00:01:51,360
Once the response is sent, that object is gone.

29
00:01:51,600 --> 00:01:52,620
It doesn't exist.

30
00:01:53,220 --> 00:01:58,920
Third is the station attribute we just got from the deepest recession object in the history.

31
00:01:58,920 --> 00:02:03,530
To be such an object itself has got from the request object, not the says.

32
00:02:03,810 --> 00:02:09,770
An object exists for that particular time period and it expires after that time period is over.

33
00:02:09,820 --> 00:02:18,300
That means the object doesn't exist, but otherwise there should be an object can exist for amongst

34
00:02:18,750 --> 00:02:24,000
various subjects like like a subject context, like an application scope.

35
00:02:24,180 --> 00:02:30,630
It can exist for for for as much time as it has been predefined opposition.

36
00:02:30,630 --> 00:02:37,840
And they should position in a letter, in the letter section, in a letter, of course, I knew about

37
00:02:37,870 --> 00:02:38,850
this decision.

38
00:02:39,150 --> 00:02:45,600
And for now you should know that these are the three scopes for our tribute request, application and

39
00:02:45,750 --> 00:02:46,350
session.

40
00:02:46,930 --> 00:02:52,680
We will cover this session, particularly in session, handling the will of the state and session and

41
00:02:52,680 --> 00:02:58,170
the different types of ways in which we can stage session, which is you are rewriting.

42
00:02:58,440 --> 00:03:04,710
He didn't field cookies and there should be such an object itself, which is a very common method,

43
00:03:04,860 --> 00:03:07,650
which is the common method of using session state.

44
00:03:07,950 --> 00:03:10,310
So we will understand session in a later course.

45
00:03:10,660 --> 00:03:14,990
OK, so this is what I wanted to tell you about in this lecture.

46
00:03:15,900 --> 00:03:16,320
Thank you.