Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#1811 closed defect (wontfix)

Operate with not responding transports

Reported by: anonymous Owned by: asterix
Priority: normal Milestone:
Component: None Version: hg
Severity: normal Keywords:
Cc: Blocked By:
Blocking: OS:

Description

When transport doesn't respond it is thought to have an old status (not offline)

Change History (9)

comment:1 Changed 11 years ago by nk

what do you mean not responding? and how did you find out it is not responding?

comment:2 Changed 11 years ago by anonymous

If I change status or try to disconnect transport manually nothing occurs. In XML console I see that message about status change or disconnect was sent

comment:3 Changed 11 years ago by asterix

  • Milestone 0.10 deleted

and you'd like that if no response after 30 sec when we send offline to a transport, we consider it offline and pass all contacts from this transport and this transport itself offline ?

comment:4 Changed 11 years ago by anonymous

I'd like to consider not responding transport offline and periodically try to reconnect it =)

comment:5 Changed 11 years ago by anonymous

And I think 30 seconds would be too short time. It's better to do 90 seconds or any time user wants

comment:6 Changed 11 years ago by nk

90 is too much. anyways we should try keep one single ACE for the CON TIMEOUT we use allover

comment:7 Changed 11 years ago by jim++

Note that you have to be sure that user didn't voluntary disconnect from transport...

comment:8 Changed 10 years ago by asterix

if the transport is dead, shouldn't the jabber server send an error

message like <not-available> ?

comment:9 Changed 10 years ago by nk

  • Status changed from new to closed

we fix Gajim, trasports devs should fix transports.

Note: See TracTickets for help on using tickets.