On 10/20/2011 03:56 AM, Dave Cridland wrote:
On Wed Oct 19 19:27:01 2011, Sergey Dobrov wrote:
The difference is that presence will be sent by server without client's
participation. And it's good from the point of traffic economy view. As
I can understand, the central target of entity
On Thu Oct 20 09:19:06 2011, Sergey Dobrov wrote:
On 10/20/2011 03:56 AM, Dave Cridland wrote:
a) Probes are sent from the bare jid.
b) Probes don't have an unavailable equivalent, needed to later
remove
the subscription.
How this solved for regular presences?
You get a later
On 10/20/2011 03:43 PM, Dave Cridland wrote:
On Thu Oct 20 09:19:06 2011, Sergey Dobrov wrote:
On 10/20/2011 03:56 AM, Dave Cridland wrote:
a) Probes are sent from the bare jid.
b) Probes don't have an unavailable equivalent, needed to later remove
the subscription.
How this solved for
just a headzup in case this is of interest..
Evented APIs
http://www.eventedapi.org/
Overview
Events indicate something has happened. In this they differ from the
request-response interaction style popular on the Web. Event-based systems are
declarative whereas request-response systems are
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: DMUC3: Distributed MUC
Abstract: This document provides a protocol for reducing the bandwidth cost of
local users contributing to a remote MUC over a constrained link through a
local mirror of the MUC room.
URL:
On 20 October 2011 17:43, =JeffH jeff.hod...@kingsmountain.com wrote:
just a headzup in case this is of interest..
Why use HTTP instead of XMPP or some other notification protocol?
There are several reasons:
1. HTTP is available everywhere online. Very few firewalls block port 80.
2.
On Thu, 2011-10-20 at 23:46 +0100, Matthew Wild wrote:
If email were just being invented today, it would use HTTP... I have
no doubt.
http://blog.mailgun.net/post/11622797058/mailgun-api-2-0-forget-mime
Just wait for them to propose that as a standard for s2s delivery.
--
Kim Alvefur
