[Standards-JIG] Message Stanza Processing

Tue Aug 24 17:47:13 CDT 2004

In light of a recent jdev post [1], I decided to go dig up a related post of 
mine from April.  It turns out that my post wasn't even logged to jdev due to 
some anti-spam filter.  So I'm posting it again, but this time to 
standards-jig (the right place), and hopefully it'll also get logged. :)

The rest of the old thread can be found at the end of the April archive [2].  
Joe suggested a JEP, which is probably the right course of action.  Any 
further thoughts?

[1] http://www.jabber.org/pipermail/jdev/2004-August/019025.html
[2] http://www.jabber.org/pipermail/jdev/2004-April/thread.html

----------  Forwarded Message  ----------

Subject: Re: [jdev] sending custom messages from one client to another
Date: Friday 30 April 2004 4:28 pm
From: Justin Karneges <justin-keyword-jabber.093179 at affinix.com>
To: Jabber software development list <jdev at jabber.org>

This reminds me of an issue I've had regarding <message> stanzas.  Since you
can have multiple top-level children with different namespaces, this leads to
a lot of different possibilities for processing a message, particularly uses
that are non-IM.  For instance, what if you get an RPC call like in your
example that contains a <body>.  Does the client perform the function,
display the body, or both?  I don't think this is defined anywhere.

I think we should have some sort of guideline that developers should follow.
Here is what I came up with:

1) If there are any 'attribute' elements like x:delay, <amp>, etc, then these
can be accounted for as they apply to any kind of message.

2) If there are elements recognized by the client as non-IM (such as IBB data
or a chat state change), then the client should process the stanza in this
way.  If there are multiple such elements, then only one kind of processing
should be performed.  Which one to choose would be implementation specific,
but probably picking the first one recognized would be fine.  End.

3) If there are elements recognized by the client as text, such as <body> or
<html>, then the message should be considered an IM.

4) However, if there are elements recognized by the client as
psuedo-attachments, such as contact items, groupchat invites, x:oob urls,
then these can be processed as either an IM (with empty body if <body> is not
present), or in a special way.

What do others think?

-Justin

On Friday 30 April 2004 11:06 am, Julian Missig wrote:
> <message to="otherclient"><body>message with an extension</body><x
> xmlns="http://myclient.web.site/protocol"><myxml><function
> attr="value"/></myxml></x></message>
>
> or use a custom IQ, depending on whether what you're doing is an
> extension of a message and you want it to be stored and forwarded, or
> (in IQ's case), you just want to call a function if the other one is
> online.
>
> Julian
>
> On 30 Apr, 2004, at 13:55, Julian Dolce wrote:
> > Hey everyone,
> >
> >
> >
> > I am pretty new to jabber and have been doing some reading and
> > searching
> > the archives on how to do this. But haven't seen a solution.
> >
> >
> >
> > What is the best way to send custom messages from one client to
> > another.
> > Basically what I want to do is be able to call a function on another
> > client.
> >
> >
> >
> > Any help or resources would be greatly appreciated.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Julian Dolce
> >
> > Creative Technologist
> >
> > Fuel Industries Inc
> >
> > Ottawa, ON
> >
> > www.fuelindustries.com
> >
> > 613.224.6738 x241
> >
> >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > https://jabberstudio.org/mailman/listinfo/jdev
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> https://jabberstudio.org/mailman/listinfo/jdev

-------------------------------------------------------