On Mar 25, 2015, at 8:34 PM, Anu Pokharel i...@monal.im wrote:
Hi all,
I make an XMPP app on iOS called Monal. Much of my comments are based on my
experiences developing an XMPP client on iOS for the past 6 years. My
concerns may be Apple specific in some places but since the intent
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
Hi all,
I make an XMPP app on iOS called Monal. Much of my comments are based on my
experiences developing an XMPP client on iOS for the past 6 years. My
concerns may be Apple specific in some places but since the intent of the XEP
is for a very general implementation, these issues should
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 Mar 10, 2015, at 8:51 AM, Christian Ulrich christian...@rechenwerk.net
wrote:
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
On Mar 10, 2015, at 8:12 AM, Christian Ulrich christian...@rechenwerk.net
wrote:
Thanks for clarifying. Do we allow a client to send an enable stanza
before resource binding then? We should not, if we want to allow the
first two options you mentioned.
I don't see a need to particularly
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
2.1 Push Service, 'is what' is extranous.
3.2 Business Rules paragraph 3, Care SHOULD be taken. 'ought' is too relaxed
a word to use here, and it doesn't fit in with the SHOULDs used in paragraph
2.
Fixed
5 Enabling Notifications, Note. This reiterates the assumption that the
App
Hello,
On 10 Mar 2015, lancest...@gmail.com wrote:
So I think using the node name as a device identifier (or more
precicely: an identifier for entities that want to receive the same
push notifications and are thus registered for the same node) is
sufficient for the xmpp server.
Yes, that
Hello Christian,
Sorry for the late reply:
On 5 Mar 2015, christian...@rechenwerk.net wrote:
So I think using the node name as a device identifier (or more
precicely: an identifier for entities that want to receive the same
push notifications and are thus registered for the same node) is
So I think using the node name as a device identifier (or more
precicely: an identifier for entities that want to receive the same push
notifications and are thus registered for the same node) is sufficient
for the xmpp server.
Yes, that is the correct interpretation. Imagine for example
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
Hello,
On 4 Mar 2015, christian...@rechenwerk.net wrote:
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
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
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 it mean ?
Suppose I am using MyApp on iPad
Hello,
On 2 Mar 2015, edi...@xmpp.org wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Push
Abstract: This specification defines a way for an XMPP servers to
broadcast information for use in push notifications to mobile and
other devices.
I have several
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
Hello,
On 3 Mar 2015, christian...@rechenwerk.net wrote:
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
On Mar 2, 2015, at 4:11 PM, Christian Ulrich christian...@rechenwerk.net
wrote:
I started implementing an older version of the XEP [1] as an ejabberd
module. It's on github [2]. Currently I'm updating it to the new
version.
Awesome and ^5!
My implementation includes the app server
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
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 at 10:46 PM, XMPP Extensions Editor edi...@xmpp.org wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Push
Abstract: This specification defines a way for an XMPP servers to broadcast
information for use in push notifications to mobile and other devices.
URL: http://xmpp.org/extensions/inbox/push.html
The XMPP Council
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
25 matches
Mail list logo
