On Thu Dec 11 10:28:40 2008, Jehan wrote:
Hum... I would consider that it would be interesting to know if a
server can store my bookmarks. On the other side, if the server
wants to
send notifications of an updated bookmark, I would think it is
interesting that it sends it only to significant c
Dave Cridland;5522 Wrote:
>
> Only those intended to be discoverable should be listed there. Some
> aren't, Bookmarks being one of them.
>
Hum... I would consider that it would be interesting to know if a
server can store my bookmarks. On the other side, if the server wants to
send notificat
On Thu Dec 11 00:17:44 2008, Jehan wrote:
But then, what if (even if it should never happen!) the other entity
set some other "node" value which is not yours?
1/ Should you anyway answer, and you give again the right node
value in
your result query?
No. That would be against XEP-0030.
2/
On Thu Dec 11 01:00:44 2008, Jehan wrote:
in the list of disco features (
http://xmpp.org/registrar/disco-features.html ), are we supposed to
have
every proposed namespace? Because I don't find for instance
"XEP-0168:
Resource Application Priority" ('urn:xmpp:rap:0' and
'urn:xmpp:raproute:0'
Hi,
Hop again about this caps XEP (sorry!).
in the list of disco features (
http://xmpp.org/registrar/disco-features.html ), are we supposed to have
every proposed namespace? Because I don't find for instance "XEP-0168:
Resource Application Priority" ('urn:xmpp:rap:0' and
'urn:xmpp:raproute:0')
Hi,
still about to this same XEP, during implementation, I came to a new
question. In the service discovery request (the one to associate a list
of features to a node), there is the "node" attribute. This attribute
can have only a single value to be consistent: the one you set in the
'c' attribut
Hi,
Dave Cridland;5492 Wrote:
>
> This message is the only one in my mailbox with this subject - maybe
> I'm missing your earlier one.
>
Here is my first message:
Jehan;5452 Wrote:
> Hi,
>
> I was rereading lately the XEP-0115 and one strange point strikes me
> (aïe!) in section "5.4 Pro
Remko Tronçon;5491 Wrote:
>
> 6.2 is about how caps information relates to the actual result of disco
> info.
> 7 describes what things you should advertise to announce your support
> for XEP-115. Every XEP has a section on what namespaces it uses. This
> one is just an edge case because you ca
On Wed Dec 10 12:59:32 2008, Jehan wrote:
Hi,
no feedback on this? Noone is interested? :-( On the same XEP, I
have
other interrogations/remarks.
This message is the only one in my mailbox with this subject - maybe
I'm missing your earlier one.
Aren't section "6.2 Discovering Capabil
> Aren't section "6.2 Discovering Capabilities" and "7. Determining
> Support" nearly the same?
6.2 is about how caps information relates to the actual result of disco info.
7 describes what things you should advertise to announce your support
for XEP-115. Every XEP has a section on what namespace
Hi,
no feedback on this? Noone is interested? :-( On the same XEP, I have
other interrogations/remarks.
Aren't section "6.2 Discovering Capabilities" and "7. Determining
Support" nearly the same?
I understand that the separation is mostly to make the difference
between the case where there is a
Hi,
I was rereading lately the XEP-0115 and one strange point strikes me
(aïe!) in section "5.4 Processing Method". It seems explained that
whether you know or not the sent entity capability verification string
"ver", you send anyway a service discovery stanza to the generating
entity!
Consideri
12 matches
Mail list logo
