The library documents itself · GUI & reactive
stzReactiveHttp
8 own methods · 0 forms written with extensions, listed under their method
the source: base/reactive/stzReactiveHttp.ring(opens in a new tab) · All classes · The area reference: GUI & reactive
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
Init
(no comment in the source: the name reads as a sentence) initno extension
SetReactor
Anything that is neither is refused rather than stored, because a bad reactor does not fail here; it fails later inside _SubmitAsync or DrainPending, a long way from the call that caused it.no extension
PendingCount
(no comment in the source: the name reads as a sentence) pending countno extension
Get_
(no comment in the source: the name reads as a sentence) get_no extension
Post
(no comment in the source: the name reads as a sentence) postno extension
Put_
(no comment in the source: the name reads as a sentence) put_no extension
Delete
(no comment in the source: the name reads as a sentence) deleteno extension
DrainPending
Called by the run loop each tick: dispatch every finished job. The curl path returns the BODY directly (headers stripped) and reports the HTTP status; success = a 2xx code (same callback contract as the blocking download() path).no extension