Sponsored Content
Full Discussion: Socket Programming
Top Forums Programming Socket Programming Post 302104960 by blowtorch on Monday 29th of January 2007 11:46:14 PM
Old 01-30-2007
Quote:
Originally Posted by Corona688
You can't declare a struct variable like "samp s1", you have to say "struct samp s1".
You could do a typedef and declare it as just 'samp s1'.

And about transferring the struct across sockets, there shouldn't be any problems there. Isn't it just a bunch of data? I thought you could transfer it just like you could transfer a string buffer.
 

10 More Discussions You Might Find Interesting

1. Programming

Socket Programming

Dear Reader, Is there any way to check up socket status other than 'netstatus ' Thanks in advance, (1 Reply)
Discussion started by: joseph_shibu
1 Replies

2. Programming

Socket Programming socket

Hello, I actually try to make client-server program. I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error : I'm just using this simple code : and I get the same error if I use : If someone can help me, Thanks (2 Replies)
Discussion started by: soshell
2 Replies

3. Programming

Need Help Regarding Socket Programming

Can anyone plz me. I need a sample code for the following description. Its urgent. It is C/Socket program with the following descriptions: NAME coreadServer - Concurrent Readers Server. coreadClient - Concurrent Readers Client. SYNOPSIS coreadServer <OutputFile> coreadClient <n>... (1 Reply)
Discussion started by: priya.vmr
1 Replies

4. IP Networking

socket programming

my system is a stand alone system... i want to try doing socket porgramming..ihave heard that this is usually done during testing... how can i do that....? (6 Replies)
Discussion started by: damn_bkb
6 Replies

5. IP Networking

socket programming

Hello Everyone Iam working on tcp/ip programming.with some time interval server has to send data.client has to close the connection and to open the connection between the time interval.this is the scenario when iam closing the connection in client side the connection terminates.how to... (1 Reply)
Discussion started by: sureshvaikuntam
1 Replies

6. Programming

help regarding socket programming

i m using sockets for setting up a connection between a server and a client. When the clients gets connected to the server, its ip is conveyed to the server through one of the predefined structures in c library... i save this ip address in an array....1st client's ip address goes to the zeroth... (1 Reply)
Discussion started by: abmxla007
1 Replies

7. UNIX for Advanced & Expert Users

socket programming

can we send udp message to a destination ip address .. without having an ip address configured in our machine using recvfrom ? (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies

8. UNIX for Dummies Questions & Answers

hi i need help with socket programming

in socket programming how can i : Create for example 3 blank files, namely: server, client, network •Server: act as servers/provider, will receive all requests from different client •Client: requesters •Network: middle-layer of communication between server & client any tips or... (6 Replies)
Discussion started by: kedah160
6 Replies

9. Programming

Socket programming

Hi everyone, I'm new to this forum. I'm working on new project for last few days and this forum already helped me on couple of occasions. I don't have any prior experience with network programming so I'll appreciate any advise given. I'm trying to do the following: 1. open user... (2 Replies)
Discussion started by: _thomas
2 Replies

10. Programming

socket programming

how to include socket.h in visual studio 2005.. (2 Replies)
Discussion started by: asd123
2 Replies
IEEE1284_TRANSFER(3)						     Functions						      IEEE1284_TRANSFER(3)

NAME
ieee1284_nibble_read, ieee1284_compat_write, ieee1284_byte_read, ieee1284_epp_read_data, ieee1284_epp_write_data, ieee1284_epp_read_addr, ieee1284_epp_write_addr, ieee1284_ecp_read_data, ieee1284_ecp_write_data, ieee1284_ecp_read_addr, ieee1284_ecp_write_addr - data transfer functions SYNOPSIS
#include <ieee1284.h> ssize_t ieee1284_nibble_read(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_compat_write(struct parport *port, int flags, const char *buffer, size_t len); ssize_t ieee1284_byte_read(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_epp_read_data(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_epp_write_data(struct parport *port, int flags, const char *buffer, size_t len); ssize_t ieee1284_epp_read_addr(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_epp_write_addr(struct parport *port, int flags, const char *buffer, size_t len); ssize_t ieee1284_ecp_read_data(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_ecp_write_data(struct parport *port, int flags, const char *buffer, size_t len); ssize_t ieee1284_ecp_read_addr(struct parport *port, int flags, char *buffer, size_t len); ssize_t ieee1284_ecp_write_addr(struct parport *port, int flags, const char *buffer, size_t len); DESCRIPTION
This set of functions is for tranferring bytes in the relevant transfer mode. For ECP and EPP modes two types of transfer are possible: data and address (usually referred to as channel in ECP). The supplied port must be a claimed port. The supplied buffer must be at least len bytes long. When reading, the transferred data is stored in the buffer; when writing the data to be transferred is taken from the buffer. For reads (peripheral to host): if no data is available and F1284_NONBLOCK is not in effect, the inactivity timer is started. If data becomes available before the inactivity time-out elapses it is read; otherwise the return value will be E1284_TIMEDOUT. For writes (host to peripheral): if the peripheral is not willing to accept data and F1284_NONBLOCK is not in effect, the inactivity timer is started. If the peripheral indicates that it is willing to accept data before the inactivity time-out elapses it is sent; otherwise the return value will be E1284_TIMEDOUT The flags may alter the behaviour slightly: F1284_NONBLOCK For reads (peripheral to host): if no data is available, return immediately (with E1284_TIMEDOUT). For writes (host to peripheral): if the peripheral is not willing to accept data, return immediately (with E1284_TIMEDOUT). F1284_SWE Don't use hardware assistance for the transfer, but instead set the parallel port pins according to the wire protocol. F1284_RLE (for ECP only) Use run length encoding. If the peripheral is in ECP mode with RLE, calls to ieee1284_ecp_read_data must set this flag in order for the RLE from the peripheral to be interpreted correctly, and calls to ieee1284_ecp_write_data may set this flag in order to take advantage of RLE. F1284_FASTEPP (for EPP only) Use multi-byte transfers. Several bytes at a time are transferred using hardware assistance, if supporting hardware is present. The price of this increased speed is that the return value will be less reliable when this flag is used. For ECP mode, a given direction is in force at any particular time, and it is up to the application to ensure that it is only writing when in forward mode, and reading when in reverse mode. RETURN VALUE
The return value is the number of bytes successfully transferred or, if negative, one of: E1284_NOTIMPL This transfer mode and flags combination is not yet implemented in libieee1284. E1284_TIMEDOUT Timed out waiting for peripheral to handshake. E1284_NOMEM Not enough memory is available. E1284_SYS There was a problem at the operating system level. The global variable errno has been set appropriately. E1284_INVALIDPORT The port parameter is invalid (for instance, perhaps the port is not claimed). If any bytes are successfully transferred, that number is returned. An error is returned only if no bytes are transferred. For host-to-peripheral transfers, all data is at the peripheral by the time the call returns. SEE ALSO
ieee1284_ecp_fwd_to_rev(3) AUTHOR
Tim Waugh <twaugh@redhat.com> Author. COPYRIGHT
Copyright (C) 2001-2003 Tim Waugh 09/18/2007 IEEE1284_TRANSFER(3)
All times are GMT -4. The time now is 02:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy