http4r

About

• http4r is based on Dan's projects utterlyidle and http-handler.rust and http4t by Matt and is based on http4k inspired by Mr Dave and Ivan Sanchez
• it is based on Server as a Function:
  • composable http handlers implement (Request) -> Response
  • immutable Request, Response, Headers etc
  • zero magic or reflection, stupidly simple and zero dependencies
  • easily test over the wire or rather in-memory
  • can test in-browser (not over the wire!) by compiling your app to WASM so we can write lightning-fast tests for our front end

GPL Copyright

http4r is a web toolkit Copyright (C) 2021-onwards Tom Shacham

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program (see COPYING). If not, see https://www.gnu.org/licenses/.

Todos

• example app
  • local webpage that loads in wasm app and runs tests
    • JSON body parser
    • read and write to database
    • checkout edge workers
    • reach out to some 3rd party api
    • do some basic auth or cookie thing

---

• request takes an into string thing rather than Uri
• client convenient method of get post etc
• build pipeline
• do not rely on nightly otherwise clients have to use it too
• core api
  • use threadpool ?
  • sort the docs out so they dont generate docs for libs
    • just generate docs in build pipeline, not committed to git
  • todos in http_test eg set-cookie header special case
  • support multipart form data and application url form encoded
  • limits on headers and body etc tests // sort out these vecs that are being allocated
  • default response headers, content-type, content-length, date
  • client to use Host header eg Dan's
  • read timeouts
  • checkout browsix
  • do we want to drop connections in stream.incoming() or do we want to hang onto them for a while
  • if version is known to be 1.0 then do not send chunked message
    • stream into memory and forward as content-length
    • support http/1.0 - ie. read til socket close or EOF
  • support Connection: close
  • bidi routing
  • support http/2.0
  • server sent events
  • websockets

Getting started

Docs coming soon

• philosophy of having recipes instead of providing library code or frameworks
• set content-encoding to none in order to override default browser accept-encoding dictating content type
• Body types, string vs stream and a diagram of the underlying model of streaming