Excited to share this blog post about some of the work @durumcrustulum and I have been doing at the @ZcashFoundation, designing a new network stack for Zcash:https://www.zfnd.org/blog/a-new-network-stack-for-zcash/ …
-
-
as a nice side effect, because connection state is isolated and each connection is an independent async task, we're automatically immune to the `ping` attack on Zcash, even though we chose this design before that attack was published :)
Prikaži ovu nit -
then, we provide a connection pool that load-balances outbound requests over all available peers, so that the rest of our code doesn't need to know about individual peer connections.
Prikaži ovu nit -
the size of the connection pool is dynamically determined by backpressure, growing when outbound request demand is high and shrinking to shed inbound request load.
Prikaži ovu nit -
this is all made possible by Tower (http://docs.rs/tower ), which provides a vocabulary for writing generic service-handling code, based on the ideas from
@marius's _Your Server As A Function_: https://monkey.org/~marius/funsrv.pdf …Prikaži ovu nit -
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.