I'm puzzled and don't think this is possible but if an application that is
running on websiteA generates a file can FTP be used from websiteA to
transfer that file to websiteB which would be located on another server?
--
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/ 7 1710
Hello,
Well it depends,
If it is the WebsiteA that is initiating the transfer to send the file
to WebsiteB, then the WebsiteB must be running an FTP Server.
If it is the WebsiteB that initiates the transfer to get the file from
WebsiteA, then WebsiteA must be running an FTP Server.
But it surely is possible.
- Vaibhav
clintonG wrote: I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Hi Clinton,
Yes, under the correct circumstances. Forgive me if I tell you anything you
already know, as I don't know what you already know, so I'm going to start
at a comfortably low position and work my way up from there...
A web application is an application designed to run in a web server. A web
server is a server application that communicates with its clients via HTTP
(HyperText Transfer Protocol). This is a text-based messaging protocol which
runs on a TCP transport over the Internet, which sends text messages back
and forth between client and server, and can also be used to transmit binary
data as well.
FTP (File Transfer Protocol) is another text-based protocol that runs on a
TCP transport over the Internet. It also involves a server (an FTP server)
and multiple clients, which transmit requests and responses in text format,
and can be used to transmit both text and binary data between server and
client.
There are several differences between these 2 protocols. FTP is a
"connected" protocol. It maintains an open connection between the client and
the server (on the server port 21 usually) for the duration of a user
session. This "command connection" is used to exchange the requests and
responses between server and client, and separate connections are created on
different ports as needed to transfer files. HTTP is a "disconnected"
protocol, which can be configured to keep the underlying TCP connection
opened, or close it and reopen it with each request/response. Because of the
"disconnected" nature of HTTP, it is stateless. It only uses a single port
(usually Port 80) to transfer all messaging and data. FTP is older than
HTTP, and has several issues with firewalls and security that HTTP does not,
but both are generally pretty reliable, as TCP is a reliable networking
protocol. They use entirely different text "languages" to communicate. And
of course, although it is theoretically possible to create an FTP client
that can render HTML, and use FTP as the underlying protocol, FTP is not
used for this purpose, and is generally regarded as simply a mechanism for
transferring files 2 ways between client and server, whilt HTTP is generally
regarded as a one-way protocol in which the client is generally only
receiving files from the server.
Enough of that. Now down to the nitty gritty of what you were asking. Both
protocols require a server to listen and handle incoming client requests.
Both protocols can run on the same machine, and can work with the same
directories. So, it is quite possible, and even common for an HTTP web to
have FTP access. Many web designers use FTP to upload their files to the web
server. So, the only real question you need to ask is, does the web server
machine have an FTP server with access to the same files and folders as the
web site? If so, an application can use both FTP and HTTP to exchange data
and files between server and client.
--
HTH,
Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist
I recycle.
I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl... I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Thanks for commenting...
<%= Clinton
"V" <va*************@gmail.com> wrote in message
news:11**********************@c74g2000cwc.googlegr oups.com... Hello,
Well it depends,
If it is the WebsiteA that is initiating the transfer to send the file to WebsiteB, then the WebsiteB must be running an FTP Server.
If it is the WebsiteB that initiates the transfer to get the file from WebsiteA, then WebsiteA must be running an FTP Server.
But it surely is possible.
- Vaibhav
clintonG wrote: I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Hello Kevin,
Thanks for the smedumacation ;-) I've never written any code that used FTP.
The concern here is ease of use and trying to provide a seamless transition
for a user on websiteA who will be using an application on websiteA that
will output an XML file that needs to be located somewhere under the root of
the user's website that I refer to as websiteB.
When the application on websiteA that generates the XML file is finished
doing so the application will ask the user if they want to see the XML file
in the browser to allow them to copy-paste or use File Save As to save to
their local file system. If they want to use a local instance of FTP to
transport the file to their website (websiteB) so be it -- or -- if
possible -- the application will ask the user to select a means to login to
websiteB from websiteA and use the application running on websiteA to
transport the file to websiteB.
I've never gotten close to any task like this. Is it clear as mud?
<%= Clinton
"Kevin Spencer" <uc*@ftc.gov> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl... Hi Clinton,
Yes, under the correct circumstances. Forgive me if I tell you anything you already know, as I don't know what you already know, so I'm going to start at a comfortably low position and work my way up from there...
A web application is an application designed to run in a web server. A web server is a server application that communicates with its clients via HTTP (HyperText Transfer Protocol). This is a text-based messaging protocol which runs on a TCP transport over the Internet, which sends text messages back and forth between client and server, and can also be used to transmit binary data as well.
FTP (File Transfer Protocol) is another text-based protocol that runs on a TCP transport over the Internet. It also involves a server (an FTP server) and multiple clients, which transmit requests and responses in text format, and can be used to transmit both text and binary data between server and client.
There are several differences between these 2 protocols. FTP is a "connected" protocol. It maintains an open connection between the client and the server (on the server port 21 usually) for the duration of a user session. This "command connection" is used to exchange the requests and responses between server and client, and separate connections are created on different ports as needed to transfer files. HTTP is a "disconnected" protocol, which can be configured to keep the underlying TCP connection opened, or close it and reopen it with each request/response. Because of the "disconnected" nature of HTTP, it is stateless. It only uses a single port (usually Port 80) to transfer all messaging and data. FTP is older than HTTP, and has several issues with firewalls and security that HTTP does not, but both are generally pretty reliable, as TCP is a reliable networking protocol. They use entirely different text "languages" to communicate. And of course, although it is theoretically possible to create an FTP client that can render HTML, and use FTP as the underlying protocol, FTP is not used for this purpose, and is generally regarded as simply a mechanism for transferring files 2 ways between client and server, whilt HTTP is generally regarded as a one-way protocol in which the client is generally only receiving files from the server.
Enough of that. Now down to the nitty gritty of what you were asking. Both protocols require a server to listen and handle incoming client requests. Both protocols can run on the same machine, and can work with the same directories. So, it is quite possible, and even common for an HTTP web to have FTP access. Many web designers use FTP to upload their files to the web server. So, the only real question you need to ask is, does the web server machine have an FTP server with access to the same files and folders as the web site? If so, an application can use both FTP and HTTP to exchange data and files between server and client.
-- HTH,
Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist
I recycle. I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:%2****************@TK2MSFTNGP02.phx.gbl... I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Hello Kevin,
Thanks for the smedumacation ;-) I've never written any code that used FTP.
The concern here is ease of use and trying to provide a seamless transition
for a user on websiteA who will be using an application on websiteA that
will output an XML file that needs to be located somewhere under the root of
the user's website that I refer to as websiteB.
When the application on websiteA that generates the XML file is finished
doing so the application will ask the user if they want to see the XML file
in the browser to allow them to copy-paste or use File Save As to save to
their local file system. If they want to use a local instance of FTP to
transport the file to their website (websiteB) so be it -- or -- if
possible -- the application will ask the user to select a means to login to
websiteB from websiteA and use the application running on websiteA to
transport the file to websiteB.
I've never gotten close to any task like this. Is it clear as mud?
<%= Clinton
"Kevin Spencer" <uc*@ftc.gov> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl... Hi Clinton,
Yes, under the correct circumstances. Forgive me if I tell you anything you already know, as I don't know what you already know, so I'm going to start at a comfortably low position and work my way up from there...
A web application is an application designed to run in a web server. A web server is a server application that communicates with its clients via HTTP (HyperText Transfer Protocol). This is a text-based messaging protocol which runs on a TCP transport over the Internet, which sends text messages back and forth between client and server, and can also be used to transmit binary data as well.
FTP (File Transfer Protocol) is another text-based protocol that runs on a TCP transport over the Internet. It also involves a server (an FTP server) and multiple clients, which transmit requests and responses in text format, and can be used to transmit both text and binary data between server and client.
There are several differences between these 2 protocols. FTP is a "connected" protocol. It maintains an open connection between the client and the server (on the server port 21 usually) for the duration of a user session. This "command connection" is used to exchange the requests and responses between server and client, and separate connections are created on different ports as needed to transfer files. HTTP is a "disconnected" protocol, which can be configured to keep the underlying TCP connection opened, or close it and reopen it with each request/response. Because of the "disconnected" nature of HTTP, it is stateless. It only uses a single port (usually Port 80) to transfer all messaging and data. FTP is older than HTTP, and has several issues with firewalls and security that HTTP does not, but both are generally pretty reliable, as TCP is a reliable networking protocol. They use entirely different text "languages" to communicate. And of course, although it is theoretically possible to create an FTP client that can render HTML, and use FTP as the underlying protocol, FTP is not used for this purpose, and is generally regarded as simply a mechanism for transferring files 2 ways between client and server, whilt HTTP is generally regarded as a one-way protocol in which the client is generally only receiving files from the server.
Enough of that. Now down to the nitty gritty of what you were asking. Both protocols require a server to listen and handle incoming client requests. Both protocols can run on the same machine, and can work with the same directories. So, it is quite possible, and even common for an HTTP web to have FTP access. Many web designers use FTP to upload their files to the web server. So, the only real question you need to ask is, does the web server machine have an FTP server with access to the same files and folders as the web site? If so, an application can use both FTP and HTTP to exchange data and files between server and client.
-- HTH,
Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist
I recycle. I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:%2****************@TK2MSFTNGP02.phx.gbl... I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Hi Clinton,
Clearer than mud! ;-)
Okay, assuming that we're talking about an XML file generated by a web
application (websiteA), and assuming that websiteB is hosted on a web server
that shares the directories with an FTP server on serverB, it should not be
a problem, except for possible security (firewall) issues.
If using .Net platform 2.0, you can use the System.Net.FtpWebRequest and
System.Net.FtpWebResponse classes to upload the file from websiteA to the
FTP server on websiteB.
I'm not crazy about these 2 classes (even though they work pretty well), as
they mimic the behavior of HttpWebRequest and HttpWebResponse, even though
under the covers, so to speak, they are doing something entirely different,
such as maintaining an opened Connection. I suppose this was a decision by
some Microsoft designer or architect who figured having 2 distinctly
different behavior models might confuse our pretty little heads. But as you
know, I'm all about personal responsibility, and believe that software
should have a programming interface that behaves the way it does. If the
developer understands nothing about the underlying protocol, he/she needs to
before he/she starts writing code. I'm all for productivity tools, but
enhancing productivity and enabling laziness and willful ignorance are 2
entirely different things, with 2 entirely opposite values.
The HttpWebRequest and HttpWebResponse classes are designed specifically to
work in and mimic the stateless "single Request/Response" model of HTTP. The
FtpWebRequest and FtpWebResponse classes are designed to work in a connected
client/server Session, but to behave as if they are working in a stateless
"Single Request/Response" situation, which they are not working in. For this
reason, if you understand much about FTP, the object model is
counter-intuitive. Of course, if you're an ignoramous, it seems perfectly
logical. But heaven help you if things don't work the way you expect,
because being an ignoramous, you will not know why, or what to do about it!
In particular, downloading files with th FtpWebRequest class is not hard at
all, but uploading them is somewhat cryptic. The reason? To upload a file,
you must create a Network Stream, and write the file to it, after agreeing
with the server on the port to send the stream to. This is all carefully
hidden in the FtpWebRequest class, and if something goes wrong, due to the
object model, it's awfully hard to figure out what. In many cases, it works
without any issues at all. In a few, you're in deep trouble.
This is why I ended up writing my own FTP client socket-based classes that
mirror the behavior of an actual FTP session, and can even log the entire
message exchange, as well as socket-related information. But that isn't
going to help you any at this point!
That said, they do the job. You may need to read a few articles to help you
learn how to use them: http://blogs.msdn.com/adarshk/archiv...gory/7225.aspx http://blogs.msdn.com/adarshk/archiv...13/229069.aspx http://geekswithblogs.net/mikeymac/a.../10/71990.aspx
In addition, here are a few pointers:
Most FTP servers that allow file uploads require a login. Be sure to use
NetworkCredentials with your FtpWebRequest to make sure that it logs in with
the correct credentials.
The key to uploading is in the FtpWebRequest.GetRequestStream method. This
encapsulates the messaging that is exchanged to set up the port to send to
on the remote server. The NetworkStream returned is actually pointing to the
Stream Socket that will be written to.
You will want to convert your XML document to a stream to upload it.
Use Passive FTP mode to ensure that firewall issues are minimized (long
story).
Be aware of potential firewall issues. FTP uses 2 connections for uploading
and downloading. Port 21 on the remote server is not likely to be an issue,
but could be. However, your client will attempt to use other ports to
transfer data. This is why you use Passive mode, since if the client on this
side of the firewall specifies a port, most firewalls will allow incoming
connections on that port.
I think that's about it. Be sure to come back if you have any problems.
--
HTH,
Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist
I recycle.
I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:eA**************@TK2MSFTNGP05.phx.gbl... Hello Kevin,
Thanks for the smedumacation ;-) I've never written any code that used FTP. The concern here is ease of use and trying to provide a seamless transition for a user on websiteA who will be using an application on websiteA that will output an XML file that needs to be located somewhere under the root of the user's website that I refer to as websiteB.
When the application on websiteA that generates the XML file is finished doing so the application will ask the user if they want to see the XML file in the browser to allow them to copy-paste or use File Save As to save to their local file system. If they want to use a local instance of FTP to transport the file to their website (websiteB) so be it -- or -- if possible -- the application will ask the user to select a means to login to websiteB from websiteA and use the application running on websiteA to transport the file to websiteB.
I've never gotten close to any task like this. Is it clear as mud?
<%= Clinton
"Kevin Spencer" <uc*@ftc.gov> wrote in message news:%2****************@TK2MSFTNGP03.phx.gbl... Hi Clinton,
Yes, under the correct circumstances. Forgive me if I tell you anything you already know, as I don't know what you already know, so I'm going to start at a comfortably low position and work my way up from there...
A web application is an application designed to run in a web server. A web server is a server application that communicates with its clients via HTTP (HyperText Transfer Protocol). This is a text-based messaging protocol which runs on a TCP transport over the Internet, which sends text messages back and forth between client and server, and can also be used to transmit binary data as well.
FTP (File Transfer Protocol) is another text-based protocol that runs on a TCP transport over the Internet. It also involves a server (an FTP server) and multiple clients, which transmit requests and responses in text format, and can be used to transmit both text and binary data between server and client.
There are several differences between these 2 protocols. FTP is a "connected" protocol. It maintains an open connection between the client and the server (on the server port 21 usually) for the duration of a user session. This "command connection" is used to exchange the requests and responses between server and client, and separate connections are created on different ports as needed to transfer files. HTTP is a "disconnected" protocol, which can be configured to keep the underlying TCP connection opened, or close it and reopen it with each request/response. Because of the "disconnected" nature of HTTP, it is stateless. It only uses a single port (usually Port 80) to transfer all messaging and data. FTP is older than HTTP, and has several issues with firewalls and security that HTTP does not, but both are generally pretty reliable, as TCP is a reliable networking protocol. They use entirely different text "languages" to communicate. And of course, although it is theoretically possible to create an FTP client that can render HTML, and use FTP as the underlying protocol, FTP is not used for this purpose, and is generally regarded as simply a mechanism for transferring files 2 ways between client and server, whilt HTTP is generally regarded as a one-way protocol in which the client is generally only receiving files from the server.
Enough of that. Now down to the nitty gritty of what you were asking. Both protocols require a server to listen and handle incoming client requests. Both protocols can run on the same machine, and can work with the same directories. So, it is quite possible, and even common for an HTTP web to have FTP access. Many web designers use FTP to upload their files to the web server. So, the only real question you need to ask is, does the web server machine have an FTP server with access to the same files and folders as the web site? If so, an application can use both FTP and HTTP to exchange data and files between server and client.
-- HTH,
Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist
I recycle. I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:%2****************@TK2MSFTNGP02.phx.gbl... I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
Kevin, you've been a real gem over the years. Your response provides me with
helpful information and insight I'm sure you gained through much painful
trial and error. I'll get right into it...
<%= Clinton
"Kevin Spencer" <uc*@ftc.gov> wrote in message
news:uo**************@TK2MSFTNGP02.phx.gbl... Hi Clinton,
Clearer than mud! ;-)
Okay, assuming that we're talking about an XML file generated by a web application (websiteA), and assuming that websiteB is hosted on a web server that shares the directories with an FTP server on serverB, it should not be a problem, except for possible security (firewall) issues.
If using .Net platform 2.0, you can use the System.Net.FtpWebRequest and System.Net.FtpWebResponse classes to upload the file from websiteA to the FTP server on websiteB.
I'm not crazy about these 2 classes (even though they work pretty well), as they mimic the behavior of HttpWebRequest and HttpWebResponse, even though under the covers, so to speak, they are doing something entirely different, such as maintaining an opened Connection. I suppose this was a decision by some Microsoft designer or architect who figured having 2 distinctly different behavior models might confuse our pretty little heads. But as you know, I'm all about personal responsibility, and believe that software should have a programming interface that behaves the way it does. If the developer understands nothing about the underlying protocol, he/she needs to before he/she starts writing code. I'm all for productivity tools, but enhancing productivity and enabling laziness and willful ignorance are 2 entirely different things, with 2 entirely opposite values.
The HttpWebRequest and HttpWebResponse classes are designed specifically to work in and mimic the stateless "single Request/Response" model of HTTP. The FtpWebRequest and FtpWebResponse classes are designed to work in a connected client/server Session, but to behave as if they are working in a stateless "Single Request/Response" situation, which they are not working in. For this reason, if you understand much about FTP, the object model is counter-intuitive. Of course, if you're an ignoramous, it seems perfectly logical. But heaven help you if things don't work the way you expect, because being an ignoramous, you will not know why, or what to do about it!
In particular, downloading files with th FtpWebRequest class is not hard at all, but uploading them is somewhat cryptic. The reason? To upload a file, you must create a Network Stream, and write the file to it, after agreeing with the server on the port to send the stream to. This is all carefully hidden in the FtpWebRequest class, and if something goes wrong, due to the object model, it's awfully hard to figure out what. In many cases, it works without any issues at all. In a few, you're in deep trouble.
This is why I ended up writing my own FTP client socket-based classes that mirror the behavior of an actual FTP session, and can even log the entire message exchange, as well as socket-related information. But that isn't going to help you any at this point!
That said, they do the job. You may need to read a few articles to help you learn how to use them:
http://blogs.msdn.com/adarshk/archiv...gory/7225.aspx http://blogs.msdn.com/adarshk/archiv...13/229069.aspx http://geekswithblogs.net/mikeymac/a.../10/71990.aspx
In addition, here are a few pointers:
Most FTP servers that allow file uploads require a login. Be sure to use NetworkCredentials with your FtpWebRequest to make sure that it logs in with the correct credentials.
The key to uploading is in the FtpWebRequest.GetRequestStream method. This encapsulates the messaging that is exchanged to set up the port to send to on the remote server. The NetworkStream returned is actually pointing to the Stream Socket that will be written to.
You will want to convert your XML document to a stream to upload it.
Use Passive FTP mode to ensure that firewall issues are minimized (long story).
Be aware of potential firewall issues. FTP uses 2 connections for uploading and downloading. Port 21 on the remote server is not likely to be an issue, but could be. However, your client will attempt to use other ports to transfer data. This is why you use Passive mode, since if the client on this side of the firewall specifies a port, most firewalls will allow incoming connections on that port.
I think that's about it. Be sure to come back if you have any problems.
-- HTH,
Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist
I recycle. I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:eA**************@TK2MSFTNGP05.phx.gbl... Hello Kevin,
Thanks for the smedumacation ;-) I've never written any code that used FTP. The concern here is ease of use and trying to provide a seamless transition for a user on websiteA who will be using an application on websiteA that will output an XML file that needs to be located somewhere under the root of the user's website that I refer to as websiteB.
When the application on websiteA that generates the XML file is finished doing so the application will ask the user if they want to see the XML file in the browser to allow them to copy-paste or use File Save As to save to their local file system. If they want to use a local instance of FTP to transport the file to their website (websiteB) so be it -- or -- if possible -- the application will ask the user to select a means to login to websiteB from websiteA and use the application running on websiteA to transport the file to websiteB.
I've never gotten close to any task like this. Is it clear as mud?
<%= Clinton
"Kevin Spencer" <uc*@ftc.gov> wrote in message news:%2****************@TK2MSFTNGP03.phx.gbl... Hi Clinton,
Yes, under the correct circumstances. Forgive me if I tell you anything you already know, as I don't know what you already know, so I'm going to start at a comfortably low position and work my way up from there...
A web application is an application designed to run in a web server. A web server is a server application that communicates with its clients via HTTP (HyperText Transfer Protocol). This is a text-based messaging protocol which runs on a TCP transport over the Internet, which sends text messages back and forth between client and server, and can also be used to transmit binary data as well.
FTP (File Transfer Protocol) is another text-based protocol that runs on a TCP transport over the Internet. It also involves a server (an FTP server) and multiple clients, which transmit requests and responses in text format, and can be used to transmit both text and binary data between server and client.
There are several differences between these 2 protocols. FTP is a "connected" protocol. It maintains an open connection between the client and the server (on the server port 21 usually) for the duration of a user session. This "command connection" is used to exchange the requests and responses between server and client, and separate connections are created on different ports as needed to transfer files. HTTP is a "disconnected" protocol, which can be configured to keep the underlying TCP connection opened, or close it and reopen it with each request/response. Because of the "disconnected" nature of HTTP, it is stateless. It only uses a single port (usually Port 80) to transfer all messaging and data. FTP is older than HTTP, and has several issues with firewalls and security that HTTP does not, but both are generally pretty reliable, as TCP is a reliable networking protocol. They use entirely different text "languages" to communicate. And of course, although it is theoretically possible to create an FTP client that can render HTML, and use FTP as the underlying protocol, FTP is not used for this purpose, and is generally regarded as simply a mechanism for transferring files 2 ways between client and server, whilt HTTP is generally regarded as a one-way protocol in which the client is generally only receiving files from the server.
Enough of that. Now down to the nitty gritty of what you were asking. Both protocols require a server to listen and handle incoming client requests. Both protocols can run on the same machine, and can work with the same directories. So, it is quite possible, and even common for an HTTP web to have FTP access. Many web designers use FTP to upload their files to the web server. So, the only real question you need to ask is, does the web server machine have an FTP server with access to the same files and folders as the web site? If so, an application can use both FTP and HTTP to exchange data and files between server and client.
-- HTH,
Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist
I recycle. I send everything back to the planet it came from.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:%2****************@TK2MSFTNGP02.phx.gbl... I'm puzzled and don't think this is possible but if an application that is running on websiteA generates a file can FTP be used from websiteA to transfer that file to websiteB which would be located on another server?
-- <%= Clinton Gallagher NET csgallagher AT metromilwaukee.com URL http://www.metromilwaukee.com/clintongallagher/
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: js |
last post by:
I am using Visual Studio 2003. An IIS is installed on a separate box
with the Remote Debugger server component from VS2003. Initially, I
created a new blank project in VS2003 under the IIS's...
|
by: Erik Sandblom |
last post by:
Hello
I can't read the London & Continental Railways website and they have no
email address to complain to. I tried calling them, but got put through to
one guy who hung up, and another who had...
|
by: Rob Dob |
last post by:
Hi,
How do I go about installing another Web Site Project inside my existing
VS2005 website project. I currently have both a forum WSP and my main WSP
application within the same solution. Both...
|
by: Tyler |
last post by:
I am developing an application which will allow me to automatically sign into
an external website. I can currently do a screen scrape using
HTTPWEBREQUEST. However I want to just redirect to the...
|
by: Kobee |
last post by:
Hi,
I'm having a few issues adapting to new 2.0 "website" project vs. the
old 1.1 "web application". One of the major issues I'm having is with
the notion of namespaces. Using the old way, I...
| |
by: crferguson |
last post by:
I'm having a really odd issue. Recently my company has upgraded our
data server. For a couple of months I'm having to host two versions of
the same website on our webserver until the new data...
|
by: Dariusz Tomon |
last post by:
Hello
I have no idea how to deploy my website to another server (in virtual folder
I cannot see dlls file). Is thate any simple and quick manner to deploy web
site to another servers?
Best...
|
by: Tessa |
last post by:
Hi,
Is there a way to use aspnet_compiler to precompile an existing asp.net 2.0
web application that is on another server?
I need to initiate the precompile programmatically from another .net...
|
by: rn5a |
last post by:
Assume that there's a website named www.abc.com. There are 2 ASPX
files & one MS-Access database file in this site. The 1st ASPX file is
named "SearchForm.aspx" & the 2nd ASPX file is named...
|
by: hmchkus |
last post by:
Hi,
How can I integrate part of information from another website on my
page?
For example, a table of schedule, weather, stock info...
I would like to know both way:
1. redirect the client...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
| |
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
| |
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |