Hello David,
Thanks for your the sockets code. I have a few questions though.
1. I realized you used TCP instead of UDP for the protocol. Are there any
advantages of one over the other besides the fact the known drawback of
standard UDP protocol (i..e, no guarantee to sequencing and
William Ampeh wrote:
1. I realized you used TCP instead of UDP for the protocol. Are there
any advantages of one over the other besides the fact the known drawback
of standard UDP protocol (i..e, no guarantee to sequencing and unreliable
delivery)?
tcp is much more popular than udp as
Hi,
An app with a ftp client ferver builtin would do the job just grand.
RFC 959 fully descibes the mechanism, plus I'm sure you could find server
code all ready implemented in perl (a client is already available as part of
libnet).
In a nutshell you have two sockets - the protocol interpreter
Thanks David.
__
William Ampeh (x3939)
Federal Reserve Board
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/ http://learn.perl.org/first-response
I have implemented something similar using named pipes instead of sockets.
For send/receive type dialog, you may be better of trying EXPECT. It is
very easy to learn, and so cool to use.
__
William Ampeh (x3939)
Federal Reserve Board
--
To unsubscribe, e-mail: [EMAIL
:
Subject: Re: coping txt files over a
peer to peer.
01/07/2004 07:01
PM
William Ampeh wrote:
Your server code will not be able to handle multiple clients. You need to
undefine $file after closing the client connection. That is:
close(FILE) if($file);
close($client);
$file = undef;#-- you omitted this line
}
good catch. thanks.
Hello David,
How would you convert your code to allow a bidirectional communication
between the clients and the server without the use of files or named pipes?
That is:
Client send a request to server, waits for server to respond,
Server processes client's request, and send response back to
William Ampeh wrote:
Hello David,
How would you convert your code to allow a bidirectional communication
between the clients and the server without the use of files or named
pipes?
That is:
Client send a request to server, waits for server to respond,
Server processes client's
Hello folks,
Howdy,
Funny I was just thinking about Sockets today.
I don't use them nitty gritty like this but I would assume you need to do multiple
send/receive/accept in a little session via your own prtocol.
Something like:
Client hello
Server howdy
Client NAME fred.txt
Server NAMEIS
Howdy,
Funny I was just thinking about Sockets today.
I don't use them nitty gritty like this but I would assume
you need to do multiple send/receive/accept in a little
session via your own prtocol.
Something like:
Client hello
Server howdy
Client NAME fred.txt
Server NAMEIS
Tino Arellano wrote:
Hello folks,
How do I send the file name used by the client so that the server uses the
same file name When it is writing it own file.
this can't be done without the client and server agree on how to retrive the
file name. one reasonable approach is let the client send
12 matches
Mail list logo
