> >I think I said that RcvdCount that a choice has to be made and Ithat I have
> >no defitive answer. The idea is to break as less as possible existing code.
> >RcvdCount is used for progress bar updating and should be compressed byte
> >count. It is also used to allocate storage (or similar use) for data and
> >should be decompressed data. Maybe for simplicity we should let RcvdCount be
> >the compressed byte count ? Really a question, the debate is open !
> I doubt that RcvdCount could be used to allocate storage. The body
> data will be put into RcvdStream that is a stream, and normally a
> stream is able to allocate the storage itself.

RcvdStream is not the only way to get data from the component. Some (many ?) 
applications sue
OnDocData event to get data on the fly.

> It could be useful if the size of the body is known in advance so the
> whole storage is allocated in one step, but eventually you have this
> information only with the content length and not from RcvdCount.
> And the content length is not always specified, not to mention the
> case when it is wrong.

If specified but wrong, the component will hang, unless the server close the 
connexion before the
length specified is reached.

> After all this considerations my conclusions are:
> - RcvdCount contains the count of bytes received from the server
> - ContentLength contains what specified in the header



To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to