If you are 100% certain that the programs that are going to communicate over ZMQ will at all times be capable of understanding each other’s binary format (eg because they are always distributed together and were all compiled with the same compiler options anyways) I see no benefit to the overhead that’s added by serialization. … Read more
You could use a protocol composition: extension Moveable where Self: protocol<Animal, Aged> { // … } Or just add the conformances one after the other: extension Moveable where Self: Animal, Self: Aged { // … }
LWT messages are not really concerned about detecting whether a client has gone offline or not (that task is handled by keepAlive messages). LWT messages are about what happens after the client has gone offline. The analogy is that of a real last will: If a person dies, she can formulate a testament, in which … Read more
Wrappers and stored properties are not allowed in swift protocols and extensions, at least for now. So I would go with the following approach mixing protocols, generics and classes… (all compilable and tested with Xcode 11.2 / iOS 13.2) // base model protocol protocol ItemViewModel: ObservableObject { var title: String { get set } func … Read more
The problem is that, in the protocol you mark the function as mutating, which you need to do if you want to use the protocol on a struct. However, the self that is passed to testFunc is immutable (it’s a reference to a instance of the class) and that is tripping up the compiler. This … Read more
the complete description of bittorrent protocol: http://jonas.nitro.dk/bittorrent/bittorrent-rfc.html
With trackerless/DHT torrents, peer IP addresses are stored in the DHT using the BitTorrent infohash as the key. Since all a tracker does, basically, is respond to put/get requests, this functionality corresponds exactly to the interface that a DHT (distributed hash table) provides: it allows you to look up and store IP addresses in the … Read more
You can just check it in: Chrome Dev Tool (F12) → Network → Protocol. It will tell you the protocol used and the domain of each transfer. Legend http/1.1 = HTTP/1.1 h2 = HTTP/2 Note: If you cannot see the Protocol column, just right-click on any header and check the “Protocol” label.