Chat program Post: 506

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Chat program Post 506 by Neo on Thursday 7th of December 2000 12:36:36 PM

12-07-2000

Administrator

TCP vs UDP

UDP can also be used in noisy environments; however the transmission control protocol that manages packet loss, sequencing, etc. must be higher in the protocol stack.

TCP does the 'transmission reliability' transparent to the application programmer. However, this does not preclude the use of higher level 'transmission reliability' on top of UDP systems.

In fact, I have worked with many companies who had issues with the overhead associated with TCP and rebuilt the transmission control model on top of UDP or RAW SOCKETS.

TCP is designed for a generic Internet end-to-end model; however it is not perfect or the most efficient for all transmission models. It is inaccurate to translate 'connectionless' UDP vs. 'connection oriented' TCP to 'unrealiable' and 'reliable'. TCP is connection oriented. UDP is not connection oriented. UDP can be used in applications where connection oriented behavior is required, it just must be done in a higher level in the stack.

We would have to start a new forum 'Advanced UNIX' or 'Advanced Networking' to further discuss, as this is not a newbies topic.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

7 More Discussions You Might Find Interesting

1. IP Networking

Implementation of chat program

Hello there! Can anybody help me out with the steps required in implementing a chat program using sockets? Bye!

2. UNIX for Dummies Questions & Answers

Chat Program

i need chat program in c. know sockets to some extent.

3. Programming

Chat client-server program

Good day everyone, I'm doing a chat client-server program:server is to receive messages from clients through a TCP port and multicast them back to all clients through a UDP port. This is my client program. I'd not know why it just sends and receives msg from server once, then it stops. Is...

4. Programming

a simple chat program

any suggestions on how i could create a simple chat program between two terminals using pipes? thanks

5. UNIX for Dummies Questions & Answers

Secure Chat program for UNIX

I am wanting to know if you have ever found an extremely secure chat program for UNIX (Solaris 7), such that I could control which users can chat with which users, ie John (teacher) can talk to Suzy (student) or Sam (student) and they can talk back to their teacher BUT there is absolutely ...

6. Web Development

Can you embed Skype or any other video chat/chat program into a webpage?

Hi, I am trying to embed Skype or any other video chat/chat program into a webpage. Has anyone had success doing this? or know how? Thanks Phil

7. UNIX for Advanced & Expert Users

Chat program between two soft terminals of my Linux machine

here i havent tried to make a communication between two terminals of different machines not either any socket program my simple aim is use ipc for chat between two soft terminals(tty's) here is my view two terminals with two applications working on same fifo one fifo b/w two terminals try...

LEARN ABOUT SUNOS

in.chargend

in.chargend(1M) 					  System Administration Commands					   in.chargend(1M)

NAME

       in.chargend - UDP or TCP character generator service daemon

SYNOPSIS

       in.chargend

       FMRI
       svc:/internet/chargen:default

DESCRIPTION

       FMRI  stands  for  Fault  Management  Resource  Identifier.  It is used to identify resources managed by the Fault Manager. See fmd(1M) and
       smf(5).

       The in.chargend service provides the server-side of the character-generator protocol. This protocol is used  for  debugging  and  bandwidth
       measurement and is available on both TCP and UDP transports, through port 19.

       The  in.chargend  service  is  an inetd(1M) smf(5) delegated service. The in.chargend detects which transport is requested by examining the
       socket it is passed by the inetd daemon.

       TCP-based service

	   Once a connection is established, the in.chargend generates a stream of data. Any data received is discarded. The server generates data
	   until the client program terminates the connection. Note that the data flow is limited by TCP flow control mechanisms.

       UDP-based service

	   The	in.chargend  listens  for UDP datagrams. When a datagram is received, the server generates a UDP datagram in response containing a
	   random number of ASCII characters (ranging from 0 to 512 characters). Any received data is ignored.

       The in.chargend data consists of a pattern of 72 character lines containing the printable, 7-bit ASCII characters. Each line is	terminated
       with a carriage return and a line feed character.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcnsu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       inetd(1M), attributes(5), smf(5)

       RFC 864

SunOS 5.10							    23 Aug 2004 						   in.chargend(1M)