Re: [twsocket] [PATCH] THttpSrv: add support for returning partialstreams

2012-02-04 Thread Arno Garrels
Tobias Rapp wrote: >> Hi! >> >> I have added a new function "AnswerStreamPart" Shouldn't that method be named "AnswerStreamAcceptRange", or at least "AnswerStreamRange"? -- Arno Garrels >> in component >> THttpConnection to allow answering partial retrieve requests using >> any tStream descen

Re: [twsocket] [PATCH] THttpSrv: add support for returning partialstreams

2012-02-04 Thread RTT
On 04-02-2012 11:25, Arno Garrels wrote: Tobias Rapp wrote: Hi! I have added a new function "AnswerStreamPart" Shouldn't that method be named "AnswerStreamAcceptRange", or at least "AnswerStreamRange"? How about if the this ranges handling code is added to the AnswerStream method? Why and

Re: [twsocket] [PATCH] THttpSrv: add support for returningpartialstreams

2012-02-04 Thread Arno Garrels
RTT wrote: > On 04-02-2012 11:25, Arno Garrels wrote: >> Tobias Rapp wrote: Hi! I have added a new function "AnswerStreamPart" >> Shouldn't that method be named "AnswerStreamAcceptRange", >> or at least "AnswerStreamRange"? >> > > How about if the this ranges handling code is adde

Re: [twsocket] [PATCH] THttpSrv: add support for returningpartialstreams

2012-02-04 Thread RTT
On 04-02-2012 16:45, Arno Garrels wrote: That's a question too, IMO accept/handle ranges should be optional and silently changing the default behaviour of an existing method is questionable, no? I totally agree with that. The server should have an options property to specify this kind of fun