06-29-2001
How to use the socket
I must write some codes about client/server architecture.
The server program send the data to the client program,And the data is huge count and I want to implement that If some error happen and traslation of the data is interrupted,The program can send the data to the client program from the pos of the data stream where is interrupted.
10 More Discussions You Might Find Interesting
1. IP Networking
how to create a socket ?
why to bind a socket?
when we use a socket? (1 Reply)
Discussion started by: amin
1 Replies
2. UNIX for Dummies Questions & Answers
hi everybody !
i want create server/clients in c++
anyone can give me i little exemple for send a string ?
or give me a good site for explain.
thx (1 Reply)
Discussion started by: mercutio
1 Replies
3. Programming
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
4. UNIX for Dummies Questions & Answers
I have been serching for a guide to unix C network programming everywhere but I have found only some tuorials, very useful but a little bit poors.
My question is if exist a network domain all over the world where C socket is treated with examples.
Programs i have looked into is hard to... (4 Replies)
Discussion started by: Davide71
4 Replies
5. IP Networking
Please need to setup a IP Socket on SCO Open Server 5.06 / 5.07 to a Linux machine.
Al that I want to do is via a simple shell command open a tcpip address, port number, and send a call to a progam with a name of a file on the linux box.
My programming language does not support socket... (1 Reply)
Discussion started by: comcaps
1 Replies
6. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
7. Programming
Hi all,
On the server side, one socket is used for listening, the others are used for communicating with the client.
My question is: if i want to set option for socket, which socket should be set on?
If either can be set, what's the different?
Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies
8. Programming
Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct...
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <string.h>
#include... (3 Replies)
Discussion started by: cyler
3 Replies
9. Programming
Dear Experts,
i am compiling my code in suse 4.1 which is compiling fine,
but at runtime it is showing me for socket programming error no 88
as i searched in errno.h it is telling me socket operation on non socket,
what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies
10. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
LEARN ABOUT SUNOS
sasl_server_start
sasl_server_start(3SASL) Simple Authentication Security Layer Library Functions sasl_server_start(3SASL)
NAME
sasl_server_start - create a new server authentication object
SYNOPSIS
cc [ flag ... ] file ... -lsasl [ library ... ]
#include <sasl/sasl.h>
int sasl_server_start(sasl_conn_t *conn, const char *mech, const char *clientin, unsigned *clientinlen, const char **serverout, unsigned
*serveroutlen);
DESCRIPTION
The sasl_server_start() interface begins the authentication with the mechanism specified by the mech parameter. sasl_server_start() fails
if the mechanism is not supported.
PARAMETERS
conn The SASL context for this connection.
mech The mechanism name that the client requested.
clientin The initial response from the client. The value of clientin is NULL if the protocol lacks support for the client-send-first
or if the other end did not have an initial send. No initial client send is distinct from an initial send of a null
string. The protocol must account for this difference.
clientinlen The length of the initial response.
serverout Created by the plugin library. The value of serverout is the initial server response to send to the client. serverout is
allocated or freed by the library. It is the job of the client to send it over the network to the server. Protocol specific
encoding, for example base64 encoding, must be done by the server.
serveroutlen The length of the initial server challenge.
RETURN VALUES
sasl_server_start() returns an integer that corresponds to a SASL error code.
ERRORS
SASL_OK Authentication completed successfully.
SASL_CONTINUE The call to sasl_server_start() was successful, and more steps are needed in the authentication.
All other error codes indicate an error situation that must be handled, or the authentication session should be quit. See
sasl_errors(3SASL) for information on SASL error codes.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlibsasl |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
gethostname(3C), sasl_errors(3SASL), attributes(5)
SunOS 5.10 1 Oct 2003 sasl_server_start(3SASL)