Re: Server/Clients system
- From: "deadpickle" <deadpickle@xxxxxxxxx>
- Date: 20 Mar 2007 12:10:43 -0700
On Mar 20, 2:05 pm, "deadpickle" <deadpic...@xxxxxxxxx> wrote:
On Mar 20, 1:48 pm, "Peter J. Holzer" <hjp-usen...@xxxxxx> wrote:
On 2007-03-20 17:20, deadpickle <deadpic...@xxxxxxxxx> wrote:
On Mar 20, 9:23 am, Ted Zlatanov <t...@xxxxxxxxxxxx> wrote:
On 20 Mar 2007 07:04:30 -0700 "deadpickle" <deadpic...@xxxxxxxxx> wrote:
d> First of all I havent wrote any code for this yet, I'm still in the
d> brainstorming section. What I want to do is have a server that resides
d> on a networked computer somewhere. This server will recieve files from
d> 2 clients. Then these 2 clients will ask the server for another file
d> and the server will send it. So in summary I have 2 Clients that can
d> send and recieve files and a Server that can recieve and send files.
d> Hope that makes sense. I am not sure on how to do this, or how to get
d> started, anyone got any ideas?
[...]Well, you could implement this with FTP or HTTP (HTTP has a "PUT"
command), reimplementing as much of the protocol as you desire. Are
you trying to implement something new as a fun project, or is this
real work? In the real world I'd avoid writing new protocols when so
many good ones exist already (implemented in C, bug-free, etc.).
This is for a undergraduate project at my university. I'm thinking
about using BitTorrent. I want this whole system to be autonomous and
to make many transfers every minute, can BitTorrent do this?
BitTorrent doesn't sound like a good choice: Firstly, it doesn't have an
upload capability (AFAIK). Secondly, it isn't designed to transfer many
small files between a server and a small number of clients - it is
designed to distribute large files to to a large number of clients.
Writing a bittorrent implementation might be fun and instructive, but
for your (stated) needs it sounds like overkill. HTTP is probably the
simplest protocol for that purpose (as long as you don't implement all
of RFC 2616).
hp
--
_ | Peter J. Holzer | Blaming Perl for the inability of programmers
|_|_) | Sysadmin WSR | to write clearly is like blaming English for
| | | h...@xxxxxx | the circumlocutions of bureaucrats.
__/ |http://www.hjp.at/| -- Charlton Wilbur in clpm- Hide quoted text -
- Show quoted text -
How about SFTP. It seems prity easy to write a script in perl.- Hide quoted text -
- Show quoted text -
Also, how can I use SFTP on a windows machine?
.
- Follow-Ups:
- Re: Server/Clients system
- From: deadpickle
- Re: Server/Clients system
- References:
- Server/Clients system
- From: deadpickle
- Re: Server/Clients system
- From: Ted Zlatanov
- Re: Server/Clients system
- From: deadpickle
- Re: Server/Clients system
- From: Peter J. Holzer
- Re: Server/Clients system
- From: deadpickle
- Server/Clients system
- Prev by Date: Re: Server/Clients system
- Next by Date: Perl/CGI file upload
- Previous by thread: Re: Server/Clients system
- Next by thread: Re: Server/Clients system
- Index(es):
Relevant Pages
|