This page (revision-90) was last changed on 24-Feb-2016 11:06 by Albrecht Striffler

This page was created on 20-Nov-2012 15:45 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
90 24-Feb-2016 11:06 9 KB Albrecht Striffler to previous
89 15-May-2014 09:33 9 KB Volker Belli to previous | to last
88 15-May-2014 09:32 9 KB Volker Belli to previous | to last
87 15-May-2014 09:30 9 KB Volker Belli to previous | to last
86 21-Jun-2013 15:09 8 KB Jochen Reutelshöfer to previous | to last
85 21-Jun-2013 15:08 8 KB Jochen Reutelshöfer to previous | to last
84 21-Dec-2012 16:15 7 KB Jochen Reutelshöfer to previous | to last
83 21-Dec-2012 16:14 7 KB Jochen Reutelshöfer to previous | to last
82 18-Dec-2012 17:47 7 KB Alex Legler to previous | to last Fix Image link URL
81 17-Dec-2012 21:33 7 KB CarstenWasner to previous | to last

Page References

Incoming links Outgoing links
Developer FAQ
Developer FAQ

Version management

Difference between version and

At line 130 added one line
In general a single d3web session is not thread-safe for write access. Reading contents from the same session with multiple threads is ok. But having an applications where multiple threads simultaneously read/write to a session, they need to be synchronized. Even if there is only one thread that writes to the session, it need to be synchronized with all reading threads. By convention, in d3web this should be done using the "Session"-Object as the semaphore for synchronization. This makes sure that your code will be interoperable with all other applications code (also considering this convention), without being in danger to create deadlocks.
At line 131 removed 2 lines
In general a single d3web session is not thread-safe for write access. Reading the session contents from multiple threads is ok. But having an applications where multiple threads simultaneously read/write to a session, they need to be synchronized Even if there is only one thread that writes to the session, it need to be synchronized with all reading threads. By convention, in d3web this should be done using the "Session"-Object as the semaphore for synchronization. This makes sure that your code will be interoperable with all other applications code (also considering this convention), without being in danger to create deadlocks.
At line 148 added one line
This page (revision-90) was last changed on 24-2月-2016 11:06 by Albrecht Striffler Top