Calminternal churn
RTSP-over-HTTP tests stop sharing listening ports
This is a quiet, test-only edition. The two RTSP-over-HTTP regression variants now receive separate RTSP and HTTP port pairs, while production units and public APIs remain unchanged.
TL;DR
- RTSPOverHTTP uses ports 3997/3996, while RTSPOverHTTPBufferedWrite keeps 3999/3998.
- The change is confined to test.net.proto and requires no Delphi or FPC application changes.
Build2.4.17369 → 2.4.17372
Commits1
Lines+10 -8
Read1 min
1 of 1 entries · 1 commits upstream
#
Entry
Category
Units
1
Low
RTSP regression variants receive independent port pairs
In test.net.proto, TNetworkProtocols.DoRtspOverHttp now accepts aRtspPort and aHttpPort instead of embedding 3999 and 3998. RTSPOverHTTP passes 3997/3996 after RunWait, while RTSPOverHTTPBufferedWrite passes 3999/3998.
Tests
test.net.proto
641d72e2+10-8
tests: TNetworkProtocols Rtsp-over-Http tests use genuine ports
Impact
The two test variants no longer reuse the same listening endpoints during a suite run. Production Delphi and FPC backends, framework behavior and public APIs are unaffected.
Units
Commits977
Active days44/60
Busiest2026-09-30
Peak60
2026-08-152026-10-13