On Di, 2015-03-10 at 01:27 -0700, Lance Stout wrote:
The defined workflow is that when the XMPP server detects something
interesting
happened, then it has a set of JID+node endpoints that can be informed of that
interesting event via pubsub publishes. We could let the server have the
option
On Di, 2015-03-10 at 00:43 -0700, Lance Stout wrote:
The intent in the security section is to not allow changing in-band what
content gets delivered via the push notifications, not the enabling/disabling
of push services.
Otherwise, a client could surreptitiously change the settings to
On Di, 2015-03-10 at 01:27 -0700, Lance Stout wrote:
I may need to add additional clarifying language to the XEP then. Enabling
and disabling as defined is for the bare JID account level. However,
servers could keep track of which services a particular resource connection
enabled and use that
On Di, 2015-03-03 at 21:55 +0100, Mickaël Rémond wrote:
Here is a very common example: I would like to receive push on my
mobile, even if my desktop client is connected. In that situation, the
message will not use offline and may not use stream management
(session
may have expired).
This is
On Mi, 2015-03-04 at 17:52 +0100, Mickaël Rémond wrote:
Well, you do not have to notify the server if the server knows that you
have two mobile devices for example a phone and a tablet. When you send
the stanza to enable push after login, it will know you are online. When
the session close, it
On Mi, 2015-03-04 at 22:23 +0100, Christian Ulrich wrote:
So I'm proposing the following:
A user MAY include a device id in the enable stanza. If he does so, the
XMPP server MUST distinguish between devices by the combination of full
jid and device id when updating the list of enabled devices
On Di, 2015-03-03 at 21:28 -0800, Lance Stout wrote:
The goal for the XEP is to let an XMPP server notify the App Servers for the
user's apps when something interesting happens. What those apps do once
notified
is up to the app's purpose and implementation. Of course, the common case we
On 03.03.2015 16:16, Mickaël Rémond wrote:
Hello,
On 3 Mar 2015,christian...@rechenwerk.net wrote:
Then the client app hands this information over to its xmpp
server using the enable-iq stanza so the xmpp server can publish push
notifications when the client app is not reachable.
What does
On Di, 2015-03-03 at 11:23 +0100, Mickaël Rémond wrote:
- Is app client really an instance of an application running on a
specific device ?
I thought at first the node what acting as a device registry, but, it
seems it does not as a node is defined as: Each PubSub node is a
delivery
On Mo, 2015-03-02 at 22:53 +0100, Daniele Ricci wrote:
I was just waiting for this :-)
Thanks to Lance and everyone that contributed to the push XEP. I'll
start experimenting with it in a few days and eventually comment the
XEP itself if I bump into practical problems.
On Mon, Mar 2, 2015
On Fr, 2015-02-13 at 15:51 -0500, Brian Cully wrote:
On 13-Feb-2015, at 13:50, Ivan Vučica i...@vucica.net wrote:
So the clients with the most enjoyable experience typically open a
connection from the developer's servers, and deliver notifications over
APNS. Should that continue to be
11 matches
Mail list logo
