contact and group retry logic update and connection awareness #276
No reviewers
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#276
Loading…
Reference in New Issue
No description provided.
Delete Branch "dan/cwtch:reconncect"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/637
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/638
@ -14,0 +13,4 @@
type contactType int
const (
peerType contactType = iota
Is is a peer type or a contact type (I prefer peer, contact has specific semantics that'd like to avoid)
what do we call what is both groups and peers?
change to connectionType and peerConn and groupConn
@ -25,3 +34,3 @@
breakChan chan bool
peers sync.Map //[string]*peer
peers sync.Map //[string]*contact
peers or contacts?
yeah the var should be called 'contacts' or? (as it has peers and groups)
Updated.
Also the previous group retry code was very bad (one uniform timeout for all conns!?! and no connection awareness.) while moving forward separate managers may be wanted, for now this is a huge improvement
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/639
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/640