Shouldn't allow multiple WebContext's to be used with the same storage location

Bug #1297924 reported by Chris Coulson on 2014-03-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
High
Unassigned

Bug Description

Currently, it's possible to create multiple WebContext objects with the same dataPath and cachePath. This is very bad, and will cause synchronization issues resulting in probable data loss and / or corruption.

We should prevent this from happening, although I'm not sure how yet.

Changed in oxide:
importance: Undecided → High
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers