Ticket #4071 (new defect)

Opened 2 months ago

Last modified 6 weeks ago

Fallback to service discovery if caps not supported

Reported by: js Owned by: asterix
Priority: high Milestone: 0.13
Component: None Version: svn
Severity: major Keywords:
Cc: OS: All

Description

It seems that Gajim is the only client supporting caps properly so far.

As we now use caps to check for features, this brings a few problems. All clients seem to support service discovery and announce for example support for file transfers. But as we only check caps, we can't send to those users. We need to do one service discovery when a user doesn't support caps and cache that. That way, we would be compatible with other clients for file transfers / MUC again.

Asterix, I guess this is a job for you :þ.

Attachments

Change History

Changed 2 months ago by misc

I can confirm the bug.

Changed 2 months ago by asterix

believe me it's not a job for me as I don't agree with this approch. But we'll talk about that in room because it will be an endless discussion.

Changed 8 weeks ago by asterix

  • milestone 0.12 deleted

for 0.12, we dno't fallback to disco, but just assume everything is supported, as it has always been the case since years. We'll see what we'll do after 0.12

Changed 6 weeks ago by js

  • milestone set to 0.13

Add/Change #4071 (Fallback to service discovery if caps not supported)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.