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,
wasn't the 3 points I raised in my 2 emails about pubsub not consistent
enough? I had no answer on any of these... :-/
Moreover the two points in my second email may be discussed, but it
looks to me that the first email is obviously a small bug in the XEP
because the title and the example
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 namespaces it
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
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 can
Hi,
as written on the devel list, I'm thinking about adding seek support to
file transfers. I'm working on media networks in my PhD thesis and a
seekable stream is exactly what I need. First a small scenario why I
think it is useful:
I have a media server with a video file. This could either be
Hi,
writing about XEP-0136.
I't seems to me that there is an inconsistency between section 7.2
http://xmpp.org/extensions/xep-0136.html#manage-retrieve
To request a page of messages from a collection the client sends a
retrieve/ element. The 'with' and 'start' attributes specify the
So, can this schema snippet from
http://xmpp.org/extensions/xep-0004.html#schema
xs:element name='field'
xs:complexType
* xs:sequence*
xs:element name='desc' minOccurs='0' type='xs:string'/
xs:element name='required' minOccurs='0' type='empty'/
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' attribute
Hi Jehan,
All of your points (in these Pubsub emails) sounded quite reasonable to me, but
I'm just a fringe subscriber...
I've been waiting on a number of Pubsub items too, but
Peter said that he was collecting the Pubsub errata
from me and would reply later, so maybe that's going on with your
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')
11 matches
Mail list logo