Elimiating buffer size transferred from Apache over sockets

This is a discussion on Elimiating buffer size transferred from Apache over sockets within the Linux Web Servers forums, part of the Web Server and Related Forums category; Hi, I hope this is the correct newsgroup. The problem I have is that I am using Apache to send ...


Go Back   Usenet Forums > Web Server and Related Forums > Linux Web Servers

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-01-2005
Ian Dean
 
Posts: n/a
Default Elimiating buffer size transferred from Apache over sockets

Hi,
I hope this is the correct newsgroup.
The problem I have is that I am using Apache to send data across the
network. The data sent is then read on a second computer using sockets.
However, this data contains a series of 3-digit hex numbers that represent
the count of characters to follow. Reading these chunks is degreading the
transfer.
Is there any settings that can be applied at either end to prevent these
counts being sent?

If it is of interest, the two computers are Alpha servers running
OpenVMS (7.1 & 7.3).
Hoping for some favourable replies,
Ian


  #2 (permalink)  
Old 04-02-2005
Juha Laiho
 
Posts: n/a
Default Re: Elimiating buffer size transferred from Apache over sockets

"Ian Dean" <Ian.d.dean@baesystems.com> said:
> The problem I have is that I am using Apache to send data across the
>network. The data sent is then read on a second computer using sockets.
>However, this data contains a series of 3-digit hex numbers that represent
>the count of characters to follow. Reading these chunks is degreading the
>transfer.


Hmm.. I don't quite believe that the effect would be that big. If it was,
it surely would've been left out of HTTP 1.1 specification.

For the rationale to use the chunked enconding, please read first
http://www.apacheweek.com/features/http11 (or at least the chapter
about chunked encoding).

It could be that you could disable the chunked encoding by specifically
requesting a non-persistent connection from the server (I didn't test
this, though), by sending a 'Connection: close' header along with the
request. But then, this'll take away the benefit you get from persistent
connections (which, of course, might not apply to your situation).

> Is there any settings that can be applied at either end to prevent
>these counts being sent?


There appears also to be something called 'blowchunks' which will deny
such client requests where chunked encoding is explicitly requested.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 07:43 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0