Go to file
Adrien Destugues ed8f28a480 Move HeadersReceived hook after parsing of cookies
I still don't get what's happening, but doing the cookie parsing at the
same time as the main thread is handling HeadersReceived seems to
trigger a memory corruption, and it will escape all my attempts to debug
it (adding printfs or any other slight change to the code will make it
go away). So just chage the order we do things and hope that's enough to
always avoid it.

As a side effect, HeadersReceived can now rely on the cookies being
already stored in the cookie jar, which I think makes more sense.

I still plan to rewrite the HTTP request code as a proper state machine,
instead of one long Run() function. This would allow to run it in
smaller steps, and thus group multiple requests in a single thread
(triggering them from poll, select, or similar).
2017-12-07 22:45:44 +01:00
3rdparty 3rdparty/kallisti5/licenseReport: Add FSF check for GPL 2017-11-28 17:13:38 -06:00
build configure: Rewrite implementation of --update. 2017-12-04 20:14:18 -05:00
data Update translations from Pootle 2017-11-25 07:09:34 +01:00
docs Update userguide and translations 2017-11-26 11:14:46 +01:00
headers build/Errors.h: Synchronize with the non-build one. 2017-12-05 18:36:11 -05:00
src Move HeadersReceived hook after parsing of cookies 2017-12-07 22:45:44 +01:00
.editorconfig editorconfig: Add new config file around our unique style 2017-09-26 14:22:32 -05:00
.gitignore .gitignore: Ignore .DS_Store (Mac OS X directory attribute files). 2016-06-18 18:25:40 -04:00
configure configure: Enable use-xattr or use-xattr-ref automatically. 2017-12-05 17:14:28 -05:00
Jamfile Jamfile: Guard against building with non-Haiku Jams. 2017-12-01 10:11:57 +01:00
Jamrules build: delete DocumentationRules. 2015-06-22 13:20:07 -04:00
License.md LICENSE: Rename to License.md, and remove all licenses but the MIT. 2016-07-29 17:36:17 -04:00
ReadMe.Compiling.md configure: Enable use-xattr or use-xattr-ref automatically. 2017-12-05 17:14:28 -05:00
ReadMe.md Partially revert "ReadMe & docs: The Haiku Book has moved to www.haiku-os.org/docs/api." 2017-02-01 15:23:54 -05:00

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:

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.