Ticket #179 (new enhancement)

Opened 4 years ago

Last modified 3 years ago

Detect when KMess can become the direct conneciton server

Reported by: diederik Owned by: diederik
Priority: normal Milestone: kmess-3.0
Component: Protocol - P2P/DC Version: 1.5-pre2
Keywords: Cc:

Description (last modified by diederik) (diff)

We need to add some check if the system can accept incoming connections.

Possible options:

  • automatic check using STUN, TURN or UPnP.
  • add a checkbox to a global "file transfer settings" panel so a system admin can disable server sockets because he knows his network setup won't be able to handle it anyway.

This setting can also be used to disable "direct connections" for MsnObject transfers. If you're behind a closed firewall, you'll have to wait for a 1 minute timeout before the data is sent. It would be better if the direct connection attempt is rejected straight away, because it's already known the DC setup won't work.

Change History

Changed 4 years ago by diederik

  • priority changed from major to normal
  • summary changed from Detect whether KMess should become the direct conneciton server to Detect when KMess should become the direct conneciton server

Changed 4 years ago by diederik

  • description modified (diff)

Changed 3 years ago by diederik

  • description modified (diff)

Changed 3 years ago by diederik

  • description modified (diff)
  • summary changed from Detect when KMess should become the direct conneciton server to Detect when KMess can become the direct conneciton server

Changed 3 years ago by diederik

  • milestone changed from kmess-2.0 to kmess-2.1

This is not very important for KMess 2.0, P2P works good enough for a 2.0 release.

Changed 3 years ago by diederik

  • milestone changed from kmess-2.1 to kmess-2.0

Correction, this one is quite useful to have (the checkbox version)

Changed 3 years ago by valerio

  • milestone changed from kmess-2.0 to kmess-2.1
Note: See TracTickets for help on using tickets.