simplex-chat / simplex-chat/simplexmq
TURN/ICE server behavior in SimplexMQ
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 847
- Forks
- 111
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
Hello! I have a few questions regarding how TURN and ICE servers work in SimplexMQ:
How do ICE servers work in the context of SimplexMQ?
I would like to understand the general architecture: at what stage are they used, and what role do they play in establishing a connection?
If multiple TURN servers are configured in the client — how is the selection between them made?
Is there a priority system, random selection, failover mechanism, or are parallel attempts used?
Is it possible to assign different TURN servers for different accounts?
For example, so that user1 uses one set of TURN servers, and user2 uses another.
How critical is the choice between UDP and TCP for TURN in SimplexMQ?
Are there any recommendations for which to use, and how does the choice affect performance and stability?
I would really appreciate any clarification!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Trace the TURN/ICE configuration and connection-establishment path in SimpleXMQ, then document server selection, per-account configuration, and UDP/TCP trade-offs.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100