Sponsored Content
Special Forums IP Networking Packetize data to send it over tcp sockets Post 302908117 by DGPickett on Thursday 3rd of July 2014 04:52:31 PM
Old 07-03-2014
TCP is a reliable stream with no packet borders, so you need to write a protocol to run inside it that defines packet size at least, if you need to recover the packets. Otherwise, just treat it like a pipe/FIFO, but bidirectional. The main trick in TCP protocols is to make sure both ends are not just reading or just sending, as that is a lockup. If you have threads or poll/select() controlled I/O then that is less of a problem (you are both reading and writing both ends all the time).

Last edited by DGPickett; 07-30-2014 at 12:37 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

Sockets donot send any thing to client

I have written a socket program in C under RedHat Linux 6.2. This program is using SOCK_STREAM (TCP) to connect to any ip address at port # 23. The program is hosted on the linux machine and works well with Cisco routers. But when I am trying to connect to the same linux machine, it does not return... (4 Replies)
Discussion started by: biswa
4 Replies

2. Programming

TCP/IP send getting slower

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower ie, the messages are not send quickly to the client. What i mean to say is since the... (0 Replies)
Discussion started by: rajesh_puru
0 Replies

3. SCO

TCP sockets

How can I change timers for TCP/IP sockets in SCO Unix 7.1.1:o (1 Reply)
Discussion started by: Dragan Travica
1 Replies

4. IP Networking

Tcp Ip Send Receive Server Program

Requirements: A server program should read a file and send the message to the client . if the file is not there, then switch to the receive part of the same program and receive any messages from the socket. If no messages to receive then switch to send part of the program to... (2 Replies)
Discussion started by: Rajeshsu
2 Replies

5. Programming

Send flaged data ..

Hello ! I'm writing a chat program , and I have a curiozity. I'm curently using two ports ( sockets ) for client - server interconections. One socket is used for ordinary ( normal ) data ( Ex : data on main-chat ) , and the another ( two socket ) is used to send management data : ( Ex... (0 Replies)
Discussion started by: !_30
0 Replies

6. Programming

problem receiving data from TCP socket

Hi all, I'm writing a socket program which sends a structure from one machine to another. When I run my client first time it runs well, however after the first time I couldn't receive all the data inside the structure (it is like, half of the array is received and the other half is not set). I... (1 Reply)
Discussion started by: SaTYR
1 Replies

7. Programming

TCP trashing data on application close

I am using c to send data to a socket with the following commands: socket = socket(AF_INET, SOCK_STREAM, ptrp->p_proto); ioctl(socket, FIONBIO, (char *)&on); connect(socket) send(socket,data) shutdown(socket, SHUT_WR); recv(socket) //ready last of data waiting on the port //note this is... (3 Replies)
Discussion started by: metrix
3 Replies

8. Shell Programming and Scripting

send data with Perl

Hello! I want to sent data (pictures: pic.jpg or textfiles) to a server. The pictures should be stored in \my_pictures\beautiful_images. How can I do it with Perl? I think, that I should start with a socket?? Do you have a tutorial or a site, where I can read about it? I use the IDE Padre /... (1 Reply)
Discussion started by: la_dy82
1 Replies

9. Programming

sockets - can you send data while waiting on select()

Hey guys, Is it possible to have a worker thread send data out a TCP connection while another thread is waiting using using select() on that same connection? If not, then what is the correct way to maintain a connection, react to incoming data, and send data over a TCP connection? Thanks... (16 Replies)
Discussion started by: scubanarc
16 Replies

10. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

I have problem with oracle solaris 10 running on oracle sparc T4-2 server. Os information: 5.10 Generic_150400-03 sun4v sparc sun4v Output from tcpstat.d script TCP bytes: out outRetrans in inDup inUnorder 6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
pppstats(8)						      System Manager's Manual						       pppstats(8)

NAME
pppstats - Print Point-to-Point Protocol (PPP) statistics SYNOPSIS
/usr/sbin/pppstats [-a] [-v] [-r] [-c count] [-w secs] [interface] [-z] OPTIONS
Displays absolute values rather than deltas. With this option, all reports show statistics for the time since the link was initiated. Without this option, the second and subsequent reports show statistics for the time since the last report. Repeats the display count times. The default repeat count is 1 if the -w option is not specified, otherwise infinity. Displays the overall packet compression rate. The rate value is between 0 and 1, with 0 meaning that the data is incompressible. Displays additional statistics, such as the number of packets ignored (rejected by the VJ TCP header decompression code). Pauses wait seconds between each display. If this option is not spec- ified, the default interval is 5 seconds. Instead of the standard display, show statistics indicating the performance of the packet com- pression algorithm in use. See the STATISTICS section for further information on this option. DESCRIPTION
The pppstats utility reports PPP-related statistics at regular intervals for the specified PPP interface. If interface is unspecified, it will default to ppp0. The display is split horizontally into input and output sections containing columns of statistics describing the properties and volume of packets received and transmitted by the interface. STATISTICS The following fields are printed on the input side when the -z option is not used: The total number of bytes received by this interface. The total number of packets received by this interface. The number of header-compressed TCP packets received by this interface. The num- ber of header-uncompressed TCP packets received by this interface. Not reported when the -r option is specified. The number of corrupted or bogus header-compressed TCP packets received by this interface. Not reported when the -r option is specified. The number of VJ header- compressed TCP packets dropped on reception by this interface because of preceding errors. Only reported when the -v option is specified. The total number of non-TCP packets received by this interface. Only reported when the -v option is specified. The compression ratio achieved for received packets by the packet compression scheme in use, defined as the uncompressed size divided by the compressed size. Only reported when the -r option is specified. The total number of bytes received, after decompression of compressed packets. Only reported when the -r option is specified. The following fields are printed on the output side: The total number of bytes transmitted from this interface. The total number of pack- ets transmitted from this interface. The number of TCP packets transmitted from this interface with VJ-compressed TCP headers. The number of TCP packets transmitted from this interface with VJ-uncompressed TCP headers. Not reported when the -r option is specified. The total number of non-TCP packets transmitted from this interface. Not reported when the -r option is specified. The number of searches for the cached header entry for a VJ header compressed TCP packet. Only reported when the -v option is specified. The number of failed searches for the cached header entry for a VJ header compressed TCP packet. Only reported when the -v option is specified. The compression ratio achieved for transmitted packets by the packet compression scheme in use, defined as the size before compression divided by the compressed size. Only reported when the -r option is specified. The total number of bytes to be transmitted, before packet compression is applied. Only reported when the -r option is specified. When the -z option is specified, pppstats displays the following fields, relating to the packet compression algorithm currently in use. If packet compression is not in use, these fields all display zeroes. The fields displayed on the input side are: The number of bytes of com- pressed packets received. The number of compressed packets received. The number of bytes of incompressible packets (that is, those which were transmitted in uncompressed form) received. The number of incompressible packets received. The recent compression ratio for incoming packets, defined as the uncompressed size divided by the compressed size (including both compressible and incompressible packets). The fields displayed on the output side are: The number of bytes of compressed packets transmitted. The number of compressed packets transmitted. The number of bytes of incompressible packets transmitted (that is, those which were transmitted in uncompressed form). The number of incompressible packets transmitted. The recent compression ratio for outgoing packets. SEE ALSO
Daemons: pppd(8) pppstats(8)
All times are GMT -4. The time now is 12:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy