🚀 go-pugleaf

"Eduardo Jauch" <eduardo.jauch@gmail.com> wrote in message
news:45e3a6cf@newsgroups.borland.com...

> This app that I'm doing, is for my personal use only. I don't mind
> if a change on the page that I access will make me re-write the
code.

You don't have to do that, though.  If you implement it properly in
the first place, then the code will automatically adapt to whatever
content it receives, so you won't have to re-write the code each time
a change occurs.

> > You are most certainly NOT handling HTTP chunked data at all !!
You
> > are not even looking at the "Transfer-Encoding" header, which
tells
> > you whether the data is chunked or not in the first place.  If it
is
> > NOT chunked, then you must use the "Content-Length" header to know
how
> > many bytes to read.
> >
>
> I sow every header of the pages that I access to see if it was
chunked
> or not, to make the code without the need to verify this every time
I
> access the page. Is bad programing, but will work until they change
the
> page, and no ptoblem with that :)

Chunking is a server-side configuration.  Many systems don't use
chunked transfers.  It actually produces more overhead than sending
the raw data as-is instead.  Chunking tends to be used only on systems
that support partial downloads, such as for resuming broken transfers.
Not all systems support that, though.

> Oh...
> But I'm stopping :)

But not as quickly as you could be.  You seem to be very fond of
writing fast running code, but you are not handling the HTTP responses
in a way that allows you to exit as soon as the response is finished.
You are sitting there waiting for a timeout that you do not need to
wait for if you take the true data length into account properly like
the RFCs say to do.

> If you look at the code, you'll see this:

Which is still the completely wrong thing to do.

> This is at the end of the loop of the recv.
> The last line "if(strcmp" is exactly verifying if the chunked block
is
> the last (because this page is chunked)

But you are not reading the individual chunks properly at all.  Which
is why you are getting into a scenerio that relies on a waiting loop
to time out.


Gambit