© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #84)
> By designing your data store to be as nonblocking as possible.
That of course is the problem. The data store in this case has already been designed, and it wasn't designed with multiple simultaneous access in mind. Redesigning the data store would potentially affect every single line of code in the entire project, as far as I can see; it's just too big a change.
Of course I don't want to discourage anyone from trying to find a clever solution. It would be great if this could be done, I'm just not optimistic.
Perhaps an emulation layer could present most of the code with what looks like a classic profile with exclusive access while actually managing simultaneous access, maybe on a copy-on-write basis?
An initial implementation might provide limited functionality (along with a warning message) for additional instances, e.g., bookmarks, history and preferences won't be remembered; I think it would still be useful, and improvements could then be made incrementally.