Hi Tomasz,
Yep, you're right. I inspected my logs again and realized that the server
does not respond with a feature var='http://jabber.org/protocol/offline'/
on disco#info.
It does however, respond with feature var='msgoffline'/
So, does that mean something useful? I guess the server does
Dnia 2008-03-17, pon o godzinie 23:17 -0700, NehaP pisze:
It does however, respond with feature var='msgoffline'/
So, does that mean something useful? I guess the server does support
offline
message handling, just in some other manner?
This is a jabberd 1.x style offline message handling.
Hi,
I am referring to the XEP 0013 specification. The spec mentions the
following
User Requests Information About Offline Message Node
iq type='get'
query xmlns='http://jabber.org/protocol/disco#info'
node='http://jabber.org/protocol/offline'/
/iq
Server Returns Information
Hi Neha,
There Might Be some minute Varying Responses across Different
Implementations of the XMPP Protocol. Not only in this case but elsewhere
too.
On Mon, Mar 17, 2008 at 5:52 PM, NehaP [EMAIL PROTECTED] wrote:
Hi,
I am referring to the XEP 0013 specification. The spec mentions the
jabberd2 seems to ignore the node value, and will always treat it as
missing. So what you're seeing is the standard reply to disco#info for the
root node.
On Mon, Mar 17, 2008 at 2:22 PM, NehaP [EMAIL PROTECTED] wrote:
Hi,
I am referring to the XEP 0013 specification. The spec mentions the
Dnia 2008-03-17, pon o godzinie 05:22 -0700, NehaP pisze:
I am referring to the XEP 0013 specification. The spec mentions the
following [...]
Well...
$ grep 0013 README.protocol
XEP-0013Flexible Offline Message Retrieval -
The server does not advertise
feature
It would still seem to be a bug though that its responding to nodes that
do not really exist, it should only be responding with the full server
details when the node attribute is not present, if it is there and the
server does not understand the particular node it should be returning a
not
Dnia 2008-03-17, pon o godzinie 14:02 +, Richard Dobson pisze:
It would still seem to be a bug though that its responding to nodes
that
do not really exist, it should only be responding with the full
server
details when the node attribute is not present, if it is there and
the
server
Hi,
I noticed that the Jabberd 2 2.1.23 server does respond to the node
attribute when the value is sessions. The namespace in this case is
http://jabber.org/protocol/disco#items. Is it that the server only does not
recognize any value for the node attribute only when the namespace is
