(Jabber == tcp) Not at all. You are discussing things at different 'levels' of the networking world.
First off, "tcp sockets" is usually used to describe the programming technique (and library) used. tcp (or more properly tcp/ip) is the protocol. It handles making the connection between the two computers and the basics of exchanging information. With retry so that the connection is reliable.
You use sockets progamming to setup the connection and code things such as "send this blob of data". Listen (receive) a blob of data from the other end. etc.
If you transfer a block of data (packet) such as 'AABBCDEFGH', what does it mean? If you do the low-level coding for sockets, well, then, it's totally up to you to interpret it.
Jabber is a protocol layered on top of tcp/ip. It uses tcp/ip to ensure that the individual packets of data are tranfered reliably. But jabber adds interpretation of the data (payload is the technical term).
Jabber also provides services such as a directory - so you don't have to know that the IP address at the other side is 192.168.1.101, it's just 'Mike'.
From where I sit, the only benefit that Jabber provides is that it's already supported by and/or figured out how to punch through the firewalls. And it has a 'file transfer' capability. So you could certainly piggy back off it. I'd need to know a lot more about the specifics of the application to say more.
-----Burton
Main Topics
Browse All Topics





by: uetian1707Posted on 2008-09-12 at 12:32:14ID: 22463130
Hi,
ki/Jabber
Yes Jabber is TCP-Based so you can get all connection-oriented features;
http://protocolinfo.org/wi