Hi Mark
I am still struggling with this problem, and are finally come to a part where I think that I can see a pattern and have theory.
But to prove my theory I need some one (Read you
) to help me.
I have for some time been focus on the data that are transmitted between the browser and the uTasker and found that all data are good and that valid.
My search for the problem has gotten me to the part where I have tried difference scenario:
1:
//#define HTTP_WINDOWING_BUFFERS 2
//#define HTTP_IGNORE_PARTIAL_ACKS
#define NO_OF_HTTP_SESSIONS 1
In this case the http speed are slow and that are expected. But when using this configuration multiple images/files are not transmitted to the browser and it is very constant.
2:
#define HTTP_WINDOWING_BUFFERS 2
#define HTTP_IGNORE_PARTIAL_ACKS
#define NO_OF_HTTP_SESSIONS 2
The speed is moderate and the images/file is transmitted most of the times received.
3:
#define HTTP_WINDOWING_BUFFERS 4
#define HTTP_IGNORE_PARTIAL_ACKS
#define NO_OF_HTTP_SESSIONS 3
The speed is high and the all the images/file are transmitted and well received by the browser.
When looking at this information I get the idea that when we have high speed and the browser never is turned down when asking for data everything is perfect.
But at low speed the browser are “turned” down some times in a wrong way and this gives the missing images/files.
So my guess it that some were in the fnHTTPListener, request that can not be handled by the uTasker are handled wrong.
Dos this makes sense or do I have a point?
See the tcp dump as ref.
Regards
Steen