But the 4 layer conversion between OSI theory and defined TCP/IP is real.
And given the case, FTP (a TCP/IP layer 4 API) is going to use layers 1-4 no
matter what. Copy or xcopy will just use just use the API layer, and allow
the network file system to independantly handle the other layers.
If this doesn't satisfiy you, you could build a couple of test machines and
SEE which works better.
"Steve Nielsen" <steve_nielsen@_blahX3_lincoln.k12.or.us> wrote in message
news:%(E-Mail Removed)...
> OSI model is theoretical. Please give a real world reason why COPY would
> be preferable over FTP on a LAN.
>
> Steve
>
> Gerry Voras wrote:
>
> > Use copy if you are on a physically conencted network and on a domain.
FTP
> > will bring in several additional layers of the OSI model into play that
> > aren't needed here.
> >
> > "ray" <(E-Mail Removed)> wrote in message
> > news:370601c4012d$4e50a2c0$(E-Mail Removed)...
> >
> >>Hi,
> >>
> >>I have users that need to transfer data from workstation
> >>to server, the data is big roughly 200MB - 300MB at a
> >>time, at the moment they are copying to a network drive
> >>which is slowing everything down.
> >>
> >>What are the advantages of using ftp rather than copying
> >>the data, would this stop any performance issues we are
> >>having with the copying of files.
> >>
> >>Thanks.
> >>
> >>Ray.
> >>
> >>
> >
> >
> >
>
|