[Bug 28230] New: Should query bare JID to check if PEP is supported

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28230

           Summary: Should query bare JID to check if PEP is supported
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: guillaume.desmottes at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


The PEP XEP says ( http://xmpp.org/extensions/xep-0163.html#support ):
"client SHOULD determine whether the account owner's server supports PEP; to do
so, it MUST send a Service Discovery [19] information request to its own bare
JID"

Currently Gabble doesn't do that but query the *server* features to check if
PEP is supported.
This used to work fine but it seems that latest ejabberd doesn't advertise PEP
in the server features any more.

We should then disco our own bare jid as well. This lead to a question: should
we block the transition to the CONNECTED state until we received the reply of
this disco (as we do for the reply of the server disco?).

If we don't then there is a risk of race: a client could try to use a PEP
feature and wrongly assume that the server doesn't support PEP because it
hasn't been discovered yet.
Also, if we don't we can't add OLPC specific interfaces once we discovered PEP
because we can't change interfaces of a connected connection.
On the other hand, we could say that we don't care because those interfaces are
about to die. Another solution could be to always claim that we support those
interfaces because it can still make sense to get OLPC info from your contacts
even if you can't publish them yourself (that's what we do with the location
interface).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.