Sponsored Content
Full Discussion: Chat program
Top Forums UNIX for Dummies Questions & Answers Chat program Post 480 by Neo on Wednesday 6th of December 2000 01:27:52 PM
Old 12-06-2000
Suggest changing the TCP socket calls to UDP, for starters.
 

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 Replies)
Discussion started by: hufs375
2 Replies

2. UNIX for Dummies Questions & Answers

Chat Program

i need chat program in c. know sockets to some extent. (4 Replies)
Discussion started by: krishnavel
4 Replies

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... (1 Reply)
Discussion started by: powermind
1 Replies

4. Programming

a simple chat program

any suggestions on how i could create a simple chat program between two terminals using pipes? thanks (1 Reply)
Discussion started by: kelogs1347
1 Replies

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 ... (1 Reply)
Discussion started by: ixeye
1 Replies

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 (2 Replies)
Discussion started by: phil_heath
2 Replies

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... (3 Replies)
Discussion started by: shyam.sunder91
3 Replies
in.echod(1M)						  System Administration Commands					      in.echod(1M)

NAME
in.echod - UDP or TCP echo protocol service daemon SYNOPSIS
in.echod FMRI svc:/internet/echo: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.echod service provides the server-side of the echo protocol. This protocol is used for debugging and bandwidth measurement and is available on both TCP and UDP transports, through port 7. The in.echod service is an inetd(1M) smf(5) delegated service. The in.echod 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.echod echoes any data received from the client back to the client. The server echoes data until the client program terminates the connection. UDP-based service The in.echod listens for UDP datagrams. When a datagram is received, the server creates a UDP datagram containing the data it received and sends it to the client. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNW | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
inetd(1M), attributes(5), smf(5) RFC 862 SunOS 5.10 23 Aug 2004 in.echod(1M)
All times are GMT -4. The time now is 06:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy