You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Glyph11 0.4.0: the engines' parse API is obsolete, and Glyph11.Pico is discontinued #972
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)
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
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
Activity
[-]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[/+]