Dnia 2008-02-07, Cz o godzinie 15:48 +0100, Ralph Meijer pisze: > > I still see a very good use case for having full JIDs on the roster: > > to communicate with different facets of the same thing. > > Ex. chrome.pl/echo and chrome.pl/broadcast > > or [EMAIL PROTECTED]/Gateway1 > > and [EMAIL PROTECTED]/Gateway2 > > You can communicate just fine with different resources directly, even > if > just the bare JID is on your roster or not on it at all. If you > receive > presence, you'll know about their availability, too.
Sure. But why do you enforce me to choose the resource every time (instead of just double clicking the contact) when I know that I will always be wanting to communicate only with the given one? -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED]
