Re: Confilct in source codes and Programming Guide?

No, there exists a temporary MemObject while reading objects from disk. See
client_side.c calls to storeCreateMemObject().

maer727@sohu.com wrote:
> Hi, pals!
>
> Here are the points taken from source codes and Programming
> Guide on MemObject.
>
> structs.h:
>
> /* This structure can be freed while object is purged out from memory */
> struct _MemObject {
> ...
> ...
>
> Programming Guide:
>
> ...
> While the object is being accessed, it also has a MemObject structure
> ...
>
> I learn from Programming Guide that there should be only one object being
> accessed and only one StoreEntry's MemObject is not NULL. But I learn from
> source codes that when the object or part of the object is in memory, its
> MemObject is not NULL. I think the latter is
> correct. Am I correct?
>
> When mentioning "accessing" in Programming Guide, is it referring to
> "be in memory"? Otherwise, it will be a conflict, IMHO.
>
> Best regards,
> George Ma
Received on Mon Apr 22 2002 - 14:09:55 MDT