RE: Data Compression

["Mike Krebs" <mkrebs@xxxxxxxxxxxxxxxxxx>]

It sounds like you are talking about HTTP compression which is actually part
of the HTTP protocol. Scott will probably jump in for a definite answer, but
I don't think HTTPAPI does compression like a browser would.

This shouldn't matter except that a bit more bandwidth is taken up. Servers
and browsers "negotiate" the compression and will do whatever the "browser"
supports.

On the other hand, if you are asking about a file being compressed and sent
down the pipe. HTTPAPI will work fine to retrieve the file and then an
appropriate tool needs to be run to untar, unzip, etc.

Mike Krebs


> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Karl Woods
> Sent: Friday, March 06, 2009 12:39 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: Data Compression
> 
> I was just asked a question by our Web Services guys: Can HTTPAPI
> handle
> compressed data. Meaning that I send a request that the returned data
> be
> compressed before sending it and then HTTPAPI decompresses the received
> data.
> 
> Karl B. Woods
> Sr. Programmer/Analyst
> Professional Services
> DriverTech, LLC
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------