Skip to content

Glyph11 0.4.0: the engines' parse API is obsolete, and Glyph11.Pico is discontinued #972

Closed

Description

@MDA2AV

Glyph11 0.4.0 (dotnet-web-stack/Glyph11#81, for dotnet-web-stack/Glyph11#58) marks its TryExtract* parse entry points [Obsolete]. They report one less than the length of the header block, which is why every call site here slices at bytesRead + 1. The replacements, TryParseRequestHeader and TryParseResponseHeader, report the length itself, so the body starts at consumed.

The engines build with TreatWarningsAsErrors, so moving to 0.4.0 does not compile until these call sites move:

Where Today With 0.4.0
Engine/Internal/Protocol/ClientHandler.cs:188 TryExtractFullHeaderValidated(ref buffer, into, Limits, out var bytesRead), then buffer.Slice(bytesRead + 1) TryParseRequestHeader(ref buffer, into, Limits, out var consumed), then buffer.Slice(consumed)
Engine/Ioxide/Protocol/Drivers/Tcp/Http1Driver.cs:157 same same
Testing/Acceptance/Engine/Body/RequestBodyLifecycleTests.cs:456, 523 same same
Benchmarks/Infrastructure/BenchmarkContext.cs:32 TryExtractFullHeaderROM(..., out _) TryParseRequestHeader(..., out _)

The rename and dropping the + 1 have to land together. Renaming alone compiles, and then every slice skips one byte: the first byte of the body, or of the next pipelined request.

Glyph11.Pico has to go in the same upgrade

Glyph11 drops its bindings (dotnet-web-stack/Glyph11#84): Glyph11.Pico and Glyph11.Native get no further releases. Glyph11 0.4.0 also stops exposing its internals to Glyph11.Pico. Pico 0.0.1 sets BinaryRequest's internal setters, so next to 0.4.0 it fails with MethodAccessException. The Glyph11.Pico dependency therefore has to be removed together with the move to 0.4.0:

Where Today Without Glyph11.Pico
Engine/Ioxide/GenHTTP.Engine.Ioxide.csproj Glyph11.Pico 0.0.1 removed
Engine/Ioxide/Protocol/Drivers/Tcp/Http1Driver.cs GENHTTP_IOXIDE_PARSER=pico switches the engine to PicoParser (benchmarking only) the switch goes; requests are always parsed by UltraHardenedParser
Testing/Acceptance/Engine/Body/RequestBodyLifecycleTests.cs:529 PicoParser.TryParse gets unvalidated framing headers into a request Glyph11's FlexibleParser.TryParseRequestHeader, which doesn't validate them either

Activity

  1. self-assigned this
    on Nov 2, 2026
  2. changed the title [-]Glyph11 0.4.0 makes the parse API the engines use obsolete[/-] [+]Glyph11 0.4.0: the engines' parse API is obsolete, and Glyph11.Pico is discontinued[/+] on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dependenciesPull requests that update a dependency file

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions