-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Even with an empty presence payload like ?
It means: I'm online with no status message (and not away/dnd/etc)
- --
Maciek A: It's against natural order of reading.
xmpp:[EMAIL PROTECTED] Q: Why is
Yup. An empty presence has just as much impact/meaning (aside
from network utilization and obviously some processing time) as one with status
information or other payload data.
-JD
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, J
Even with an empty presence payload like ?p.s Answering below quoted text is similarly annoying for people with mobile email clients where only the first X bytes are retrieved by default ;-)- Original Message From: Maciek Niedzielski <[EMAIL PROTECTED]>To: Jabber software development lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Assuming (for legacy reasons), the only injection point available in
> the code for this uni-directional "keepalive" is a message or
> presence packet, how "bad" is it to send a to the server
> (vs. say a jabber:iq:version o
Sending a to a server is probably the worst thing
you could possibly do for a keep-alive. J Aside from login and logout,
and some more complicated JEP’s like MUC or PubSub, it’s the most
intensive operation an XMPP server performs and in most cases causes multiple hits
to the back end data
Assuming (for legacy reasons), the only injection point available in the code for this uni-directional "keepalive" is a message or presence packet, how "bad" is it to send a to the server (vs. say a jabber:iq:version or jabber:iq:time) ?Will most servers ignore this safely and will it be consider
Stephen,
It's essentially doing connection aggregation. And, yes, the client
maintains the connection to the CM for the life of the session. To a
client, the CM looks exactly like any normal XMPP server.
The are some other interesting use cases for CM's. For example, an
external HTTP binding prox
Matt, out of interest - does the connection manager aggregate many c2s
connections into a smaller set of streams or does it handle the
authentication process and pass authenticated streams to the Wildfire server
or does it do something else? Does the client maintain a connection to the
connection m
