If you to the minimal stuff required for a HTTP POST request you get:
Quelltext
1: 2: 3: 4: 5: 6:
| POST /file.php HTTP/1.1 Host: hostname Content-Length: 30 Content-Disposition: Attachment
YourDataYourDataYourDataYourDa |
on upstream
and
Quelltext
1: 2: 3: 4:
| 200 Ok Content-Length: 3
Yes |
on downstream (on best case) (in Normal both require much more data).
Thus you get about 130 Bytes up and 29 Bytess down (not including the about 200 Bytes TCP\IP overhead).
Using that information I get about 1,5 MB traffic per day. (359 Bytes per Request)
Optimizations:
- Use a GET-Request instead of POST (shorter Requests)
- Generate the HTTP-GET-Requests your own (using a socket)
- See if you can save some more bytes ...
What you can't is get below the TCP overhead of about 200 Bytes per Request.
Why don't you write your own server application that handles this in shorter form? Then you had 231 instead of 359 Bytes per Request (about 1MB\day).
You can't get much below that ...
Anyone who is capable of being elected president should on no account be allowed to do the job.
Ich code EdgeMonkey - In dubio pro Setting.