Couple of things:
First of all, you use port 8080 for this daemon, which strikes me slightly as odd. Of course you are free to use any port available, but port 8080 is usually used as an alternative for HTTP.
Secondly, I miss authentication/security ;) This daemon -as I see it- allows connections from everywhere and is ok with the idea that the client is giving the filename. I don't know much about the win32 OS (which you seem to use), but imagine this on a *NIX machine and I decide to upload some text file with a filename of "/etc/passwd" and "/etc/shadow". (Ok, true enough, running this daemon as root is stupid to begin with ;) I'm sure there are files on your OS that you'd rather see not updated by the clients. Using authentication at least gives you someone to blame when things go ugly, and of course, please do check the filename input.
Finally, have you considered the already available alternatives, such as ftp, sftp/scp, rsync (does that exist on win32?)? You could even write an upload CGI script, and let your http daemon "handle" the connections.
Just my €0.02
In reply to Re: Client(s) sending file(s) to server using Sockets
by b10m
in thread Client(s) sending file(s) to server using Sockets
by rupesh
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |