Opened 14 years ago

Closed 13 years ago

#71 closed task (worksforme)

*TM-REVISION* --> thread-safety

Reported by: lgiessmann Owned by: lgiessmann
Priority: critical Milestone: miscellaneous 2010
Component: data-model Version: 0.1
Keywords: Cc:

Description

make the variable *TM-REVISION* thread-safety, since it is accessed during reading and writing (also in the restful interface);

solution define a function *TM-REVISION-R* that uses a the reader lock and a function *TM-REVISION-W* that uses the writer-lock; both function should access the variable *TM-REVISION* that should be declared as private; change all occurrences of *TM-REVISION*

Change History (5)

comment:1 Changed 14 years ago by lgiessmann

Status: new → accepted

comment:2 Changed 14 years ago by lgiessmann

the same for *CURRENT-XTM* *DOCUMENT-ID*

comment:3 Changed 14 years ago by lgiessmann

the same for *JSON-XTM*

comment:4 Changed 14 years ago by lgiessmann

A possible solution could be a local let-variable named *TM-REVISION* that is initialized with the current version and hides the actual global variable d:*TM-REVISION*

comment:5 Changed 13 years ago by lgiessmann

Resolution: → worksforme
Status: accepted → closed

the implemented method works, sonce *TM-REVISION* is not used in the hunchentoot-handlers, because an explicit revision is given

Note: See TracTickets for help on using tickets.