> > eg when I am at work, I sign in to [EMAIL PROTECTED]/work and subscribe to the J2J > > transport that logs me into [EMAIL PROTECTED]/home - now my co-workers and > > customers can see me online as me@work, and my friends see me online as > > [EMAIL PROTECTED], but I only need to run one Jabber client and it doesn't need > > to be modified in anyway to handle multiple accounts. > > Psi (psi.sf.net) can already handle multiple accounts concurrently.
Yes I know - a design flaw IMO, and not what I had in mind. There needs to be a *server side* solution. The Jabber design philosophy has always been to keep the client simple and move the complexities to the server. There are other solutions of course, such as running multiple instances of your client, or modifying all clients to log into multiple servers, but they are not really practical or elegant. If you want to go that way, you may as well install Trillian and let your client log into every server under the sun - no need for Jabber at all. Michael. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
