Ticket #23 (closed bug: fixed)

Opened 12 years ago

Last modified 12 years ago

Different requests modifying the same callbacks dict

Reported by: bertrand.croq Owned by: apoirier
Priority: major Component: uncategorized
Version: 0.1.0 Keywords:


When Nagare receives a first request R1, it gets the associated session then extracts the callbacks dict Cdict1 from this session. Then, the requested callbacks are called ; this modifies the callbacks dict. Finally, the new callbacks dict Cdict2 is stored in the session.

A problem occures when a second request R2 is received for the same session before Cdict2 is stored : this second request will start working on the callbacks dict Cdict1 and will produce another callbacks dict Cdict3.

If R1 finishes before R2, all the new callbacks registered is Cdict2 will be lost because Cdict3 will replace it in the session.

If R2 finishes before R1, all the new callbacks registered is Cdict3 will be lost because Cdict2 will replace it in the session.

Change History

comment:1 Changed 12 years ago by apoirier

  • Status changed from new to closed
  • Resolution set to fixed

(In [e8c7134f63c2175488142886b3b4408374e103e5]) Fixes #23. Session lock added

Note: See TracTickets for help on using tickets.