Home/Modules/http

http

system module http

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

<img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-logo-004.jpg" alt="SLeeLa">

SLeeLa HTTP

This directory contains the HTTP transport, negotiation, protocol specifications, and web-integration layer for SLeeLa.

The complete generation family is organized as http-1.0/ through http-9.0. HTTP 1.0/1.1 are compatibility targets; HTTP 2.0 through 9.0 are SLeeLa-specific application/protocol generations and are not presented as official Internet HTTP versions.

The HTTP subsystem is intended to provide a conventional Internet-facing transport while keeping SLeeLa business logic behind a defined connector boundary.

Structure

The HTTP 3.0 implementation source (crypto capsules, key distribution, route navigation, and the build/self-test tooling) lives in the top-level http-3.0/ directory.

The implementation should remain compatible with ordinary HTTP infrastructure, including routers, proxies, TLS termination, fiber, coax, Ethernet, Wi-Fi, and other underlying physical/network media.

HTTP Version Port-Multiplexing Model

SLeeLa documents one common application-level port model across its HTTP generations:

The layers remain distinct:

native transport endpoint → HTTP stream → SLeeLa logical port → service/operation

A logical port identifies a service, channel, endpoint, virtual listener, or application route. It is not a promise that the host has opened a corresponding TCP/UDP socket for every logical value.

Common Large-File Download Mode

All SLeeLa HTTP generations share a logical DOWNLOAD mode for files larger than 50 MB. HTTP 1.0 uses its request/connection model, HTTP 2.0/2.1 uses HTTP/2 streams, and HTTP 3.0 uses QUIC/HTTP/3 streams. The resume identity is independent of transport.

SESSION-ID | DATETIME | FILE-ID | FILE-NAME | INDEX | OFFSET | TOTAL-SIZE

FILE-ID identifies the file transfer. INDEX identifies its segment/chunk and OFFSET identifies its byte position. This allows a new request or stream to resume an interrupted transfer.

Native HTTP server configuration, logging, and outputs

The runnable server grades live under ../http-servers/. Their current server-specific configuration interface is the command line; the general config/sleela.properties.example file is not implicitly consumed by these listeners. Grade 3 additionally requires a TLS private key, certificate, and QUIC-capable backend.

Operational logging and generated artifacts are documented separately:

HTTP/3 runtime diagnostics are emitted through the service's standard error stream and the selected QUIC backend; private keys, certificates, logs, and generated binaries are deployment/runtime artifacts rather than HTTP source data.


SLeeLa

<p align="center"><img src="images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>

Files 50