Re: Moving files from clients to the server

From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 08/30/04


Date: Mon, 30 Aug 2004 01:41:29 -0700

The standard approach would be to use sockets, but
I honestly don't know if that's the best solution for you.

-- 
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Kalevet" <Kalevet@discussions.microsoft.com> wrote in message 
news:E304C330-005D-4F77-BB4B-73E28EF45EDD@microsoft.com...
> Hi all,
> I'm working on a system that involves clients that reproduce certain 
> files,
> and a server that processes them. I have a dilemma regarding the way the
> files should be passed to the server. The problem is that the files might 
> be
> as large as a few tens of MB, and there might be a few tens of files.
> Therefore, the fastest way to create them is on the clients' machines.
> However, the server expects to see them on its local disks as well, to 
> avoid
> extra networking while they are processed.
> When dealing with files, nothing makes more sense then using the file 
> system
> interface (explorer, dos commands, windows API) for moving them from one
> computer to another. This, however, requires some sort of folder sharing 
> and
> having the proper rights. We install our system at various clients, each
> having a different network, and I can't tell how happy would the system
> administrator be with sharing folders. Also, I'd like to have the file 
> move
> automated, since I can't be sure the clients would remember to do that 
> every
> time.
> Another solution is to steam the files over the network. I use DCOM to
> communicate between the clients and the server. I assume passing 100MB 
> files
> using the file system would be done more efficiently then streaming them 
> and
> passing them as strings using DCOM calls (what are the limits for that?), 
> but
> I'd like to hear your opinion about that. What I like about this solution 
> is
> that it takes the users and the network configurations out of the game, 
> but I
> really don't know if that's reasonable or not.
> If you have any other idea as to how to move files from the clients to the
> server while depending as little as possible on the users and the network
> configuration, I'd love to hear it.
> All users use windows, the network could be either netware or windows.
> Thanks,
> Kal
> 


Relevant Pages

  • RE: Printing from Win9x clients stops
    ... > and make sure this software does not interfere with SBS Server. ... > clients, please disable it and try again. ... Create a local printer and redirect the port to the network server. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... ISA2k4 is currently not supported on SBS ... To review - you have LAN clients that you want to have ... card for your server. ... > network with 5 client computers. ...
    (microsoft.public.windows.server.sbs)
  • RE: Users Cant Access Documents on Server
    ... Thanks for using the SBS newsgroup. ... As well as we know, if a workstation would not access network shares, then ... Leave the Default Gateway of the internal NIC blank of the server box. ... Clients That Require SMB Signing ...
    (microsoft.public.windows.server.sbs)
  • Solved: FreeBSD as print server w/CUPS + samba + apsfilter
    ... CUPS and Samba so that local (connected to server) printers print ... as network printer amongst Windows 2k/XP clients. ... samba over Win2k network" contained what I had accomplished, ...
    (freebsd-questions)
  • ie 6.0
    ... > laptop moves from one network to another, its IP address lease might need ... > request might go to a different server that will not extend the lease ... > for a period of time, it will not provide the time to requesting clients. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)