On Mon, Sep 26, 2011 at 10:55 PM, Kurt Zeilenga kurt.zeile...@isode.com wrote:
On Sep 26, 2011, at 2:36 PM, Peter Saint-Andre wrote:
5. Both subject/ and body/ in a single message
(A message with a subject/ and a body/ is a legitimate message,
but it SHALL NOT be interpreted as a subject
On Sep 26, 2011, at 11:09 PM, Kevin Smith wrote:
I think one ought to allow for extension elements in the subject change
message. For instance, say the subject change message is delayed at an
occupant's server, which hence adds a delay/ element. Hence, I think it
should be a subject/
On Tue, Sep 27, 2011 at 2:36 AM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 9/19/11 11:34 PM, Waqas Hussain wrote:
3. Service changing room nick
I'd like some text stating that a service can change the occupant's
nick at any time, including room join. An occupant MUST listen for
status
On Tue, Sep 27, 2011 at 2:13 AM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 9/24/11 1:53 PM, Waqas Hussain wrote:
I note that this feature has no disco feature defined.
MUC does not have the plethora of disco features that PubSub has. You
decide whether that's a good thing or a bad
Hi all,
We are currently developing Jabber-RPC based interactions in a distributed
application.
We use the base64 type to transmit binary data over the wire and we are
facing a compatibility issue between client and server implementations:
The capitalization of the 'Base64' element seems to be
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Unique Room Names for Multi-User Chat
Abstract: This specification defines an XMPP protocol extension for requesting
a unique room ID from a multi-user chat service.
URL: http://xmpp.org/extensions/inbox/muc-unique.html
On 9/27/11 7:59 AM, Gerard Maas wrote:
The question is: is Base64 (in uppercase) a typo in the schema or is
it the correct definition for it and must be respected by the
implementations?
I think the uppercase B is a typo in XEP-0009.
Peter
--
Peter Saint-Andre
https://stpeter.im/
On Tue Sep 27 16:39:51 2011, Peter Saint-Andre wrote:
On 9/27/11 7:59 AM, Gerard Maas wrote:
The question is: is Base64 (in uppercase) a typo in the schema
or is
it the correct definition for it and must be respected by the
implementations?
I think the uppercase B is a typo in XEP-0009.
On 9/27/11 9:47 AM, Dave Cridland wrote:
On Tue Sep 27 16:39:51 2011, Peter Saint-Andre wrote:
On 9/27/11 7:59 AM, Gerard Maas wrote:
The question is: is Base64 (in uppercase) a typo in the schema or is
it the correct definition for it and must be respected by the
implementations?
I
On Tue Sep 27 16:51:39 2011, Peter Saint-Andre wrote:
XML element names are case-sensitive.
Ah, yes, indeed. For some reason I'd assumed it was an attribute name
and obviously failed to properly read the original mail, sorry.
Dave.
--
Dave Cridland - mailto:d...@cridland.net -
On Tue Sep 27 16:53:58 2011, Dave Cridland wrote:
On Tue Sep 27 16:51:39 2011, Peter Saint-Andre wrote:
XML element names are case-sensitive.
Ah, yes, indeed. For some reason I'd assumed it was an attribute
name and obviously failed to properly read the original mail,
sorry.
Attribute
On 9/27/11 9:51 AM, Peter Saint-Andre wrote:
I will reach out to Elliotte Rusty Harold about this to see if he's
received any errata about this in his book.
Done. I'll post again if I hear from him.
/psa
On Tue, Sep 27, 2011 at 6:00 PM, Peter Saint-Andre stpe...@stpeter.imwrote:
On 9/27/11 9:51 AM, Peter Saint-Andre wrote:
I will reach out to Elliotte Rusty Harold about this to see if he's
received any errata about this in his book.
Done. I'll post again if I hear from him.
Many
On 9/27/11 10:07 AM, Kurt Zeilenga wrote:
On Sep 27, 2011, at 8:35 AM, XMPP Extensions Editor wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Unique Room Names for Multi-User Chat
Abstract: This specification defines an XMPP protocol extension for
On Sep 27, 2011, at 9:10 AM, Peter Saint-Andre wrote:
On 9/27/11 10:07 AM, Kurt Zeilenga wrote:
On Sep 27, 2011, at 8:35 AM, XMPP Extensions Editor wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Unique Room Names for Multi-User Chat
Abstract: This
The payment-required stream error was afaik removed from XMPP Core, so
should it be removed from XEP 60? It could be moved to the pubsub#errors
namespace.
http://xmpp.org/extensions/xep-0060.html#subscriber-subscribe-error-payment
--
Kim Alvefur z...@zash.se
On 9/27/11 10:20 AM, Kim Alvefur wrote:
The payment-required stream error was afaik removed from XMPP Core, so
should it be removed from XEP 60?
Thanks for the bug report. XEP-0060 needs another round of cleanup to
correct such errors, so I'll add this to the list. :)
It could be moved to
The problem have it's begging in this ejabberd ticket:
https://support.process-one.net/browse/EJAB-1473
I have small microblogging experimental project based on XEP-277, when
user wants to read some user, he sends subscribe presence. Another user
automatically sends subscribed but he doesn't
Depending on what the problem one is trying to solve by server generation
of the name instead of client side generation, possibly so.
If reservation is desired and to be required of servers, that that should
be clearly stated.
I note that this would prevent a user from asking the server to
On 9/27/11 11:28 AM, Bernard Aboba wrote:
Depending on what the problem one is trying to solve by server
generation of the name instead of client side generation, possibly so.
If reservation is desired and to be required of servers, that that
should be clearly stated.
On 9/27/11 7:38 AM, Waqas Hussain wrote:
On Tue, Sep 27, 2011 at 2:13 AM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 9/24/11 1:53 PM, Waqas Hussain wrote:
I note that this feature has no disco feature defined.
MUC does not have the plethora of disco features that PubSub has. You
decide
On 9/27/11 7:29 AM, Waqas Hussain wrote:
On Tue, Sep 27, 2011 at 2:36 AM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 9/19/11 11:34 PM, Waqas Hussain wrote:
3. Service changing room nick
I'd like some text stating that a service can change the occupant's
nick at any time, including room
Am 27.09.2011 18:26, schrieb Peter Saint-Andre:
On 9/27/11 10:20 AM, Kim Alvefur wrote:
The payment-required stream error was afaik removed from XMPP Core, so
should it be removed from XEP 60?
Thanks for the bug report. XEP-0060 needs another round of cleanup to
correct such errors, so I'll
On 9/27/11 3:28 PM, Alexander Holler wrote:
Am 27.09.2011 15:29, schrieb Waqas Hussain:
11. Full-to-bare JID rewriting to support vCards
All(?) implementations are doing it, but it's not specified anywhere.
Should it be?
Yes, it should. Proposed text would be appreciated.
Err... a
Am 27.09.2011 19:33, schrieb Peter Saint-Andre:
On 9/27/11 11:28 AM, Bernard Aboba wrote:
Depending on what the problem one is trying to solve by server
generation of the name instead of client side generation, possibly so.
If reservation is desired and to be required of
25 matches
Mail list logo
