You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Using a single socket and simply passing messages to two different handlers would be much more optimal. #307
The current system halves the amount of connections we can have due to FD limits. We also have to track has live/has sync leading to issues such as #290. Finally, it's likely a bit more CPU intensive.
The most annoying part of this would be Transactions; we wouldn't immediately be able to tell if it's a response to a SyncRequest or just a new Transaction. It shouldn't matter in practice, especially as we can still track rejections via DataMissing, yet would complicate some internals.
Activity
kayabaNerve commentedon May 17, 2021
The most annoying part of this would be Transactions; we wouldn't immediately be able to tell if it's a response to a SyncRequest or just a new Transaction. It shouldn't matter in practice, especially as we can still track rejections via DataMissing, yet would complicate some internals.