On 4 Aug 2025, at 04:04, Michael De Roover <[email protected]> wrote:
> [...] And that's what I
> actually want for these ATtiny85 chips in situ. They will have a serial
> interface for whenever I want to interface with them and probe their internal
> state. But for the most part, they will be shouting into the void.
Your application seems like it is plausibly one-way ("I tell you regularly
about my sense of time" does not invite a reply or a triggering question) and
that the scope of the announcement is naturally limited (to whatever you plug
into your repurposed GPIO pins). By contrast, shouting into the void from
well-connected DNS servers is a known hazard and imposes costs on third parties.
Requiring a session to be established as a bar to entry is a feature which
comes with a cost on the server (e.g. dealing with failed setup and teardown)
and on the client (e.g. setup overhead and its impact on transaction latency)
but it avoids the costs of not requiring a session. As has been widely noted,
those costs of session establishment also exist for other successful protocols
that are sensitive to latency and which often involve short-lived transactions.
Joe
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
