On 05-02-2012 12:15, Arno Garrels wrote:
I see. A new method then (and "AnswerStreamAcceptRange" seems more
Or, probably better, replace the AnswerStream code with the new one that
handle ranges, and with a new parameter (e.g. SendRangeIfValid)
application can control the behavior by request basis. These methods
share almost all the code, so it's more easy to maintain this way. And,
if really needed to maintain backward compatibility, define a overload
AnswerStream, without that parameter, that calls the new one.
So there must be an option to allow
ranges on a per request basis. A new method would provide such an option.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be