That's actually a really fun question. =) The original reason I got
into Jabber was because of transports. I loved the idea of:
1. Connecting to one and only one chat service
2. Still being able to talk to all my friends from said one connection
3. Not having to pass up clients because they only supported one
account at one time
4. Not having to pass up clients that -only- did XMPP
5. Not having to remember a bizillion usernames and passwords each
time i switched clients
[at the time i had trouble remembering my icq number, for example)
Now, that said, now instead of connecting to multiple protocols, I
end up connecting to multiple xmpp accounts. So what exactly did I
buy there? Not sure. =) At some level, I find the entire process
of learning their protocols and working with them to be fun. And of
course, I'd never actually catch problems if I wasn't actually -
using- my transports.
Daniel
On Dec 20, 2006, at 5:51 PM, Bearcat M. Sandor wrote:
I was using the transports on my own server for my old uses. No other
users are expected to log on. Then i moved over to the world of
gnome for
awhile and gaim does not support loading services, so i started
using the
native IM protocols instead. Now i am back in KDE.
Using the transports, you have 3 points of failure: jabber, python
and the
transport itself. It seems that file transfers don't work as well.
Are there times when a transport would be recomended, other then
the pride
of having it connect to my own server?
Really, if i'm the only one using it, are there advantages over native
connections?
Thank you,
Bearcat M. Sandor
_______________________________________________
py-transports mailing list
[email protected]
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
_______________________________________________
py-transports mailing list
[email protected]
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
