12-06-2005
If you're just about to send a text string to another socket server you can simply use Netcat (netcat or nc) if it's avaiable @ SCO.
read the manpages.
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. Programming
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... (1 Reply)
Discussion started by: niuzefeng
1 Replies
3. 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
4. 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
5. 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
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 SUSE
net::server::proto::ssl
Net::Server::Proto::SSL(3) User Contributed Perl Documentation Net::Server::Proto::SSL(3)
NAME
Net::Server::Proto::SSL - Net::Server SSL protocol.
SYNOPSIS
See Net::Server::Proto.
DESCRIPTION
Experimental. If anybody has any successes or ideas for improvment under SSL, please email <paul@seamons.com>.
Protocol module for Net::Server. This module implements a secure socket layer over tcp (also known as SSL). See Net::Server::Proto.
There is a limit inherent from using IO::Socket::SSL, namely that only one SSL connection can be maintained by Net::Server. However,
Net::Server should also be able to maintain any number of TCP, UDP, or UNIX connections in addition to the one SSL connection.
Additionally, getline support is very limited and writing directly to STDOUT will not work. This is entirely dependent upon the
implementation of IO::Socket::SSL. getline may work but the client is not copied to STDOUT under SSL. It is suggested that clients
sysread and syswrite to the client handle (located in $self->{server}->{client} or passed to the process_request subroutine as the first
argument).
PARAMETERS
In addition to the normal Net::Server parameters, any of the SSL parameters from IO::Socket::SSL may also be specified. See
IO::Socket::SSL for information on setting this up.
BUGS
Christopher A Bongaarts pointed out that if the SSL negotiation is slow then the server won't be accepting for that period of time (because
the locking of accept is around both the socket accept and the SSL negotiation). This means that as it stands now the SSL implementation
is susceptible to DOS attacks. To fix this will require deviding up the accept call a little bit more finely which may not yet be possible
with IO::Socket::SSL. Any ideas or patches on this bug are welcome.
LICENCE
Distributed under the same terms as Net::Server
THANKS
Thanks to Vadim for pointing out the IO::Socket::SSL accept was returning objects blessed into the wrong class.
perl v5.12.1 2007-02-03 Net::Server::Proto::SSL(3)