W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 2000

Re: programming questions and design questions

From: Benoit Mahe <Benoit.Mahe@sophia.inria.fr>
Date: Thu, 15 Jun 2000 13:50:52 +0200
Message-ID: <3948C31C.A99E33BE@sophia.inria.fr>
To: "Yanick Gamelin (LMC)" <lmcyaga@lmc.ericsson.se>
CC: "'zzJigSaw W3'" <www-jigsaw@w3.org>
"Yanick Gamelin (LMC)" wrote:

> Hi jigPeoples,
>         I try to understand the design you done by reading in the code
> (backward ingeneering) and it cost me a lot of time,
> 1- i need to know if it possible to remove the hastable "entries" in the
> resourceStoreManager by saving/retrieving the stores directly with the
> primarykey  you use in the hastable (or something else)? i mean, store file
> will be named by a integer value

Yes, I think it's possible.

> 2- i don't understand why you set a ressource to "modified = true" each time
> it was accesed, unless looking if that resource is, or is not, in the store.
> This mean, that each open store will be saved back to disk without regarding
> if new element were added. How may i can fix this ??

Where did you read this? I can't find it, but as you describe it, it seems to be a bug.
A Store is not supposed to be saved if it was no modified.

> 3- How can i keep up to date the store file with the store in memory,(by
> calling the methode save() in the methode markModified())  -->see point
> 2<--, it mean a lot of disk access...  Maybee it must be useful to add a
> variable (boolean used) by side of variable modified.

Well, if you want to keep it up to date, the only way it to save it each time it
is modified. I don't really understand what the second solution is supposed to do...

Regards, Benoit.

- Benoît Mahé -------------------------------------------------------
                      World Wide Web Consortium   (W3C)
                    Architecture domain - Jigsaw Engineer

                http://www.w3.org/People/Mahe  - bmahe@w3.org
Received on Thursday, 15 June 2000 07:50:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:36 UTC