[Standards-JIG] RE: Standards-JIG Digest, Vol 12, Issue 2

Jean Louis Seguineau jean-louis.seguineau at antepo.com
Tue Jan 4 14:49:51 UTC 2005


The 'repltyto' of JEP33 is definitively the way to go. The JEP exists, and
the broadcast mechanism described is only one way to use it.

Jean-Louis Seguineau
Director, product Engineering
Chief Software Architect
Antepo, Inc. ( www.antepo.com )
-----Original Message-----


Message: 9
Date: Mon, 03 Jan 2005 11:58:36 -0500
From: Nolan Eakins <sneakin at semanticgap.com>
Subject: [Standards-JIG] Re: Syntax for forwarding messages
To: standards-jig at jabber.org
Message-ID: <crbtfa$6ep$1 at sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Remko Troncon wrote:
>>Funny you mention this, because i'm actually needing this for JEP-146. 
>>I wrote something about that up a few months ago
>>	http://www.cs.kuleuven.ac.be/~remko/jabber/forwarding.txt
> 
> 
> The corresponding draft for this simple extension is here:
> 	http://www.cs.kuleuven.ac.be/~remko/jabber/forwarding.html

A forwarding/routing slip JeP has been on my todo list to base a couple of
other JEPs on. Seeing how the above is a start, I would recommend using 0033
as a base. 0033's schema allows a lot more than this forwarding JEP. It
would just need to be an informational JEP on how to use 0033 for forwarding
instead of multicasting. The only conflict that could occur is if the
message is sent to a multicasting component instead of an endpoint that can
forward stanzas.

There would also need to be a way to tack on the amount of time spent at
each hop. This was a feature request for another JEP that I need to spend
some more time on. It's available at
http://semanticgap.com/jeps/translation.html if you'd like to see how I was
planning on using 0033 to forward stanzas.

I hope that helps.

- Nolan





More information about the Standards mailing list