Read-only archive of the All About Symbian forum (2001–2013) · About this archive

Tcp/ip for connections?

6 replies · 2,902 views · Started 11 July 2003

Can someone please explain to me what TCP/IP is and what is the difference of using a wap protocol and TCP/IP for connections...

That is a good question but the answer is not exactly short 😊 I suggest you browse google on the same subject in read up.

-Edit-

I've been trying to answer your question clearly and simple as i possible and i've been having hard time to do so withouth starting a crazy rambling envolving all aspects of networking and internet :roll:

Wap stands for Wireless Application Protocol and it is a way(simple protocol acutally) to bring the web to a wap enabled mobile device,be it a PDA a smartphone or a regular mobile phone.Wap consists of a client side micro browser and a server side on which the micro browser services and applications reside.

TCP/IP consists of two segments(TCP and IP) and basicaly it the backbone of the internet,its the protocol universal to all OS's used for communication between LAN's WAN's used to bring "can't live without" services like file sharing,e-mail,network gaming to the user.

While WAP is not so wide spread you can find a PC in almost every home using TCP/IP to connect to the internet or a small Lan or anything else.So what is the benefit of using TCP/IP instead of Wap?My guess is,standardization(Is this a word?),easier access to the internet,easy implementation of internet services(not just www) and a lot more.

Note that this is something that came out of distorted mind on a really hot day and it could be wildly innacurate.

Let me try but please correct me if anything wrong.
TCP/IP is a protocol stack which include network protocol and transport protocol
In a simply word, TCP/IP used to control the data transfer from one device to another. U can think we need air to transfer our sound wave to other (BTW, TCP/IP is not so relevant to air because air is the media while TCP/IP is not, they are actually far differents). without LANGUAGE we can't make other know what we mean, instead they only hear our sound.
WAP is the LANGUAGE. A device can TALK WAP we call it WAP server (like something we call it the web server?), the WAP data transfer using the TCP/IP protocol stack, then the WAP data reach our phone.
Do u know WAP? Actually I don't know, so I need a translate software, which is a WAP browser (called micro browser right?). Finally we can c text and picture that what we need.

I agree with you steve,WAP and TCP/IP are quite different and i don't think you can compare them,your explanation was excelent.

[quote="steve01"]...WAP is the LANGUAGE. A device can TALK WAP we call it WAP server (like something we call it the web server?), the WAP data transfer using the TCP/IP protocol stack, then the WAP data reach our phone.
Do u know WAP? Actually I don't know, so I need a translate software, which is a WAP browser (called micro browser right?). Finally we can c text and picture that what we need.[/quote]

Need to correct this... WAP is not a language, but a bunch of specifications defining a standard for mobile Internet application and browsing. Markup language used in WAP is either WML or XHTML, depending of the WAP version.

Benefits for using TCP/IP: bigger file download, no need for conversions in the gateway -> more reliable.