The cookie jar used to be locked whenever an iterator was instanciated. This didn't work well when using several iterators in the same thread, because the BLocker then allows all of them to access the list concurrently. Rework the locking code to use a more fine grained approach, where the cookie jar is only locked temporarily by methods which require it. These methods are the ones which get and put new domain-lists in the jar, as well as acquiring the locks on the domain-lists. Each domain-list in the jar is locked using a read/write lock as before. This means there can be many requests getting cookies for the same domain in paralel, but only one at a time is allowed to set new cookies. The iterators keep domain lists they need to access read-locked, as long as they iterate the cookies for that domain. A limitation of this approach is that deleting a domain-list when it becomes empty is difficult. We can live with this, however, the iteration still works (it just skips empty lists), and the empty lists will not be stored or restored when archiving the cookie jar.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.