History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: FC-1423
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Matthew Bryant
Reporter: Jason Betz
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FarCry Core Framework

Persistant content objects suffer thread safety issues with unscoped vars when webskin is applied

Created: 01/Aug/08 05:31 AM   Updated: 13/Aug/08 11:30 AM
Component/s: Libs (FAPI, etc)
Affects Version/s: 3.0.2, FarCry 4.0 (Gonzalas), FarCry 5.0 (Fortress), 4.0.9, 4.0.10
Fix Version/s: 5.0.2

Time Tracking:
Original Estimate: 1 hour
Original Estimate - 1 hour
Remaining Estimate: 1 hour
Remaining Estimate - 1 hour
Time Spent: Not Specified
Remaining Estimate - 1 hour

Environment: All


 Description  « Hide
If content objects are persisted (by ColdSpring for example), getView() suffers thread safety issues because any variables in the webskin that are in the "variables" (default) scope are global to the entire content object and can be reassigned by other threads. (IE, not var'd).

This occurs because the main mechanism for applying the webskin is via a cflinclude.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Geoff Bowers - 11/Aug/08 02:17 PM
My understanding is we're going to require webskin developers to use either stparam or stobj scopes for local variables.

Mat can you confirm the agreed way forward here and close out the ticket if appropriate.

Geoff Bowers - 12/Aug/08 11:16 AM
Added to stobj and stparam structures, a new local structure called stlocal.