Go to file
Adrien Destugues a9665fc66a HttpRequest: use data from the input buffer first
The HttpRequest protocol loop is designed using an input buffer storing
data from the socket. At each loop, we try to parse some of the data,
and then read more from the socket.

However, in some cases (in particular with chunks, which we parse only
one at a time in a loop iteration), we may not use all the data from the
buffer. Eventually, we will be left with an "empty" socket (nothing to
read from there) but the request not completed because there is still
data in the input buffer.

In that case, we would hang waiting for a read on the socket, instead of
processing data from the input buffer.

Change the code to read from the socket only if a loop iteration did not
manage to read anything from the input buffer. This means the input
buffer is too small for the next thing to process (it contains less than
one line of data, for example), and in that case we can safely read from
the socket without being blocked.

This should fix several cases where the network code was stuck doing
nothing, including https://my.justenergy.com/ reported in #13010.
2016-10-31 22:00:40 +01:00
3rdparty 3rdparty/qtcreator: Totally new version of the create_project_file script. 2016-10-22 02:09:56 -04:00
build Re-build of libevent, update to transmission package. 2016-10-28 08:56:41 +02:00
data Update translations from Pootle 2016-10-29 08:06:47 +02:00
docs docs/develop: Create a 'bluetooth' directory. 2016-10-19 19:18:14 -04:00
headers Url: implement same URL parsing logic in C/C++ code 2016-10-31 09:14:44 +01:00
src HttpRequest: use data from the input buffer first 2016-10-31 22:00:40 +01:00
.gitignore .gitignore: Ignore .DS_Store (Mac OS X directory attribute files). 2016-06-18 18:25:40 -04:00
configure arm: Add beaglebone target, rename beagle 2016-10-20 11:05:46 -05:00
Jamfile Switch to tiff4 as system dependency. 2015-10-18 10:00:02 +02: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 Added hint to have an updated "bison" for compiling on OS X 2015-12-22 17:46:39 +01:00
ReadMe.md ReadMe: HaikuPorts has moved to GitHub. 2015-06-30 10:03:49 -04: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.