Repository navigation
Conversation
JohnAmadis
left a comment
There was a problem hiding this comment.
@JaxCalder Do poprawy
| strategy: | ||
| fail-fast: false | ||
| matrix: | ||
| tools: [arch/x86_64, arch/armv7/cortex-m4, arch/armv7/cortex-m7] |
There was a problem hiding this comment.
nie wpisujemy zadnego matrixa recznie. Kod przeciez nie jest machine specific wiec nie ma sensu marnowac czasu CI na budowanie na kazda architekture
| contents: write | ||
| strategy: | ||
| matrix: | ||
| arch_name: [x86_64, armv7/cortex-m4, armv7/cortex-m7] |
There was a problem hiding this comment.
od tego masz skrypt new-module.sh aby on poprawnie zainicjalizowal CI. To jest zle
| ) | ||
|
|
||
| dmhttp_audit_module(${DMOD_MODULE_NAME}) | ||
| dmod_link_modules(${DMOD_MODULE_NAME} dmosi dmtls) |
There was a problem hiding this comment.
co to jest ten audit module?
| @@ -0,0 +1,11 @@ | |||
| find_package(Python3 REQUIRED COMPONENTS Interpreter) | |||
| function(dmhttp_audit_module target) | |||
| # Metadata is checked at build time and excluded from the binary by objcopy. | |||
There was a problem hiding this comment.
to nie jest potrzebne. Jesli masz problemy z globalbymi pointerami to je usun. Jesli uzywasz zewnetrznych bibliotek to zrob ich forka i z nich tez to usun
| @@ -0,0 +1,4 @@ | |||
| # dmhttp documentation | |||
|
|
|||
| - [API and contracts](api.md) | |||
There was a problem hiding this comment.
to jest glowna dokumentacja, ktora uzytkownicy zobacza po wpisaniu dmf-man. Serio?! uwazasz ze ma tak wygladac? czy ty w ogole sie zainteresowales czym jest ten dmf-man i po co ten folder w ogole istnieje?!
| DMHTTP_ERR_PROTOCOL = -7, | ||
| DMHTTP_ERR_LIMIT = -8, | ||
| DMHTTP_ERR_TRUNCATED = -9, | ||
| DMHTTP_ERR_TIMEOUT = -10, |
There was a problem hiding this comment.
czemu one sie nie zgadzaja ze standardem? np z tego co pamietam 404 to not found a nie widze go tu
|
tak brzydkiej implementacji to ja dawno nie widzialem |
Implement a DMOD HTTP/1.1 download library with streamed GET/HEAD over a nonblocking connector and verified dmtls. Initialize with the standard library/GitHub generator, without a driver/port layer.
The state machine handles Content-Length, chunked framing/extensions/trailers, EOF-delimited bodies, relative redirects, byte ranges, cancellation, bounded parser storage and a finite total transaction deadline. It rejects ambiguous/malformed framing, truncation, unsupported encodings, certificate/hostname failures and HTTPS downgrades. Normal completion and redirects send TLS close_notify. Applications own connector readiness, entropy/UTC and trust-store provisioning; the body is never accumulated in RAM. The interface covers GET/HEAD, with scope/ownership documented in include/dmhttp.h and docs/api.md.
Production dependencies are unversioned dmosi and dmtls. SDK/loader and 240-byte DMF format are unchanged. There is no custom pointer audit or additional linker flags; request callbacks are stored per instance. Native/M4/M7 builds have been validated. M7 image is 10368 bytes DMF / 8031 bytes DMFC, plus request state and separate TLS/transport memory.
Validation:
The validated MCU configuration includes choco-technologies/dmtls#2. Some longer ECC-chain public-server attempts remain intermittent after slow handshakes; this is recorded separately in choco-technologies/dmtls#3, not presented as a passing case. Verification remains mandatory. Raw logs and private fixture keys stay local. Renode was omitted as requested.
Registry: choco-technologies/dmod-registry#21. Ecosystem: choco-technologies/dmod-ecosystem#33. Publish first releases before registry binary installation.
CI and release workflows use the standard
new-module.shlibrary/GitHub templates: native CI runsdmf-get/dmod_loader, and release architectures are discovered automatically. The only added steps install test dependencies and run HTTP interoperability CTest. No Makefile wrapper is included.The installed
dmf-man dmhttppage covers setup, options, request lifecycle, event scheduling, HTTP statuses, resuming downloads and troubleshooting.dmf-man dmhttp apidocuments function contracts and local errors. Both pages were checked through the actual viewer from the generated package layout. Named HTTP status constants preserve standard numeric values; local operation results remain separate.