Re: Thread-safe caches

PC> It may also be acceptable that the caches are not always updated, so if
PC> new entries in the caches are actually not written every now and then,
PC> that's fine, as long as the caches remain consistent...

i think plists are thread-safe when setq, rplaca and rplacd are atomic,
which i believe is true.
as for consistency question, it depends on nature of this cache -- are
concurrent incompatible updates possible and what to do in this case.
e.g. is it possible that one thread deletes entry while another updates it?


.

Relevant Pages

  • Re: creating ExecuteQuery method
    ... caches and re-uses compiled delegates (thread-safe) ... I did minor testing and commited your code. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: exim4 doesnt connect to smarthost
    ... and thought I'd post a response to explain what is going on in ... no connections using tcpdump. ... caches, called exim_dumpdb, exim_tidydb, and exim_fixdb. ... entries, ...
    (Debian-User)
  • RE: Enterprise Manager
    ... You probably just needed to do a refresh on the appropiate collection in enterprise manager - it caches the entries. ... "mike" wrote: ...
    (microsoft.public.sqlserver.programming)
  • Automatic `nodump flag?
    ... to be excluded from the regular filesystem dumps. ... new entries appear in the caches, ... nodump flag set. ...
    (freebsd-questions)
  • Re: Thread-safe caches
    ... i think plists are thread-safe when setq, rplaca and rplacd are atomic, which i believe is true. ... concurrent incompatible updates possible and what to do in this case. ... Cache entries are never deleted. ...
    (comp.lang.lisp)