{#}  Replies are directed back to [EMAIL PROTECTED]
{#}  To reply to the author, write to Eric Peyton <[EMAIL PROTECTED]>


On Wednesday, February 27, 2002, at 08:59  AM, Derek J. Balling wrote:

> {#}  Replies are directed back to [EMAIL PROTECTED]
> {#}  To reply to the author, write to "Derek J. Balling" 
> <[EMAIL PROTECTED]>
>
> a.) Is there any way to set the Resource for the Jabber signon (e.g. 
> "Work", "Home", "Laptop")?
>

Nope.

> b.) If I get a message from "user@jabberserver/Home", I'm being told 
> that I'm replying to simply "user@jabberserver", which may (or may not) 
> get to the user (depending on their client-resource/priority settings). 
> Is this a known bug? Basically every time my boss sends me a message I 
> end up replying to his home machine, because it has the higher priority 
> value[1].
>
> Any thoughts on this?
>

The jabber client I did was pretty bare bones.  I am still not sold on 
the whole jabber scheme (especially their "resources") and as such never 
even thought about tackling it a year or more ago when I did it.

Jabber is by far the least used Fire service (with IRC bringing up a 
close 2nd) and as such it gets almost no attention.

Eric


> D
>
> [1] Never mind the logical argument that the priority-value scheme 
> Jabber uses is hokey, and that the different clients should 
> auto-calculate their priority based on which order they were last used 
> in rather than arbitrary values which may be right NOW, but not LATER.
> -- +---------------------+-----------------------------------------+
> | [EMAIL PROTECTED]  | "Thou art the ruins of the noblest man  |
> |  Derek J. Balling   |  That ever lived in the tide of times.  |
> |                     |  Woe to the hand that shed this costly  |
> |                     |  blood" - Julius Caesar Act 3, Scene 1  |
> +---------------------+-----------------------------------------+
>
> {#} ----------------------------------------------------+[ fire ]+---
>
>


{#} ----------------------------------------------------+[ fire ]+---


Reply via email to