回复:Re: Confilct in source codes and Programming Guide?

Thanks, Henrik pal!

I read storeCreateMemObject() and find it is simply to create
the MemObject of a store StoreEntry if the StoreEntry dose not
have the MemObject.

I am puzzled that when a StoreEntry has a MemObject and when
the MemObject of a StoreEntry is purged. Can you give me a
simple explanation?

I think there could be more than one StoreEntry whose MemObject is not
NULL. Am I correct?

Best regards,
George Ma

----- 原文 -----
From: Henrik Nordstrom
To: maer727@sohu.com ;squid-dev@squid-cache.org
Cc: squid-dev@squid-cache.org
Subject: Re: Confilct in source codes and Programming Guide?
Sent: Tue Apr 23 04:09:47 CST 2002

> 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 - 19:23:46 MDT