[jdev] How can I reduce the (duplicated) stanzas sent?

[Norman Rasmussen]

On 5/24/06, Lines, David <David.Lines at uk.thalesgroup.com> wrote:
> An example of a 'redundant' stanza is when requesting access to a chatroom;
> a <request to room at server <mailto:room at server> > is sent with a <priority>
> =0 parameter. A response is received and then another request is sent
> identical to the previous but instead with only <priority> = 5 changed. Is
> there a way I can simply set this <priority>=5 in the first instance and
> remove the need for the 'duplicate' stanza? I notice this 'duplication'
> occurs when presence information is also sent when another client joins the
> chatroom, so if I can eliminate this for all C/S connections I can greatly
> reduce the chattiness of the whole network.

That's an implementation bug, the protocol doesn't "require" that you
do weird things like that.

> Also when a client wants to connect the stanzas requests are as follows;
>
> 1.< version> and <stream>
> 2. <iq to address> and <username>
> 3. as above with <resource> and <digest>
> ....
> Other stanzas
>
> My questions are why is stanza #3 sent in addition to #2? Can this
> <resource> and <digest> information be included in previous stanza via
> standard configuration options?

SASL requires that the server sends the client a challenge first, if
you wanted to avoid the round trip you could change to non-sasl and
lose security.  (The client is only allowed to bind it's resource once
it's logged in to the account, hence the seperate stanzas)

-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/