[Standards-JIG] Re: proto-JEP: Stream Acking

Justin Karneges justin-keyword-jabber.093179 at affinix.com
Wed Oct 27 07:39:05 UTC 2004

Nothing changed.

It's funny you bring up single-character acking, considering JEP-0017 came up 
recently, which also wanted to throw stuff into the <stream> CDATA.  I feel 
we shouldn't even go there.  We have namespaced elements for a reason.

However we could pick a shorter namespace or a short element name (kinda like 
JEP-0115) just to reduce size.  You could also declare another namespace 
prefix in the stream tag.


On Wednesday 27 October 2004 12:03 am, Nolan Eakins wrote:
> First off, has anything changed since the last time this was seen?
> And secondly, I know some other people other than myself liked the idea of
> using single characters for at least the acking. I'm not entirely sure if
> this would be in accordance with XMPP-Core, but it would be a 40 (if I
> recall) some byte savings per ack. I expect there to be plenty of acking
> going on too.
> - Nolan
> JEP Editor wrote:
> > The JEP Editor has received a proposal for a new JEP.
> >
> > Title: Stream Acking
> >
> > Abstract: This JEP defines a mechanism for acking over streams.
> >
> > URL: http://www.jabber.org/jeps/inbox/ack.html
> >
> > In accordance with JEP-0001, the Jabber Council will decide within 7 days
> > whether to accept this proposal as an official JEP.

More information about the Standards mailing list