Will representation of data structure in memory is known as Ever Die?
in the memory representation, the data structure is called the page, since the memory space in which it resides is referred to as a page.
The reason we need a page is because the page is the unit of memory access, but that doesn’t mean that every part of the page is a part of the object.
So, the page may be a part of the object, but the page may not be a part of the object. For example, let’s say we have a document in the database. The only way we can get to it from the file system is by using the indexer to traverse the document. Because a file is a list of pages, the indexer must iterate through the list of pages to find the page to access.
So, we know the page is a part of the object, but we need to be a bit more precise about what it is.
Of course, we can’t just say the page is a part of the object, because it could be a part of the object and yet not be a part of the object. So that’s why the object must contain the page as a part of it.
This is where things get ugly. Because we’re using the definition of the object to be a part of the object, we’re saying that the object is the page. But we’re also saying that the page is the object. The object could have an indexer, a document, and an object, but all of these things are not the same thing.
I think the biggest mistake people make when they’re trying to figure out what a page actually contains is to take things too literally. Take a look at the definition of an object. The first thing you see is “a container that has an indexable set of contents”. But this is like saying, “Look, it’s a picture, so it’s a picture”. What people tend to take literally is “the page is a part of the object”.
I am the type of person who will organize my entire home (including closets) based on what I need for vacation. Making sure that all vital supplies are in one place, even if it means putting them into a carry-on and checking out early from work so as not to miss any flights!