Am 05.07.2005 um 09:41 schrieb Stephen Deasey:
Does anyone have a small bugfix they need to add? I'll add the change
for varargs macros so the Windows compile works. Anything else?
Not at the moment. I'm happy with what we have now.
Zoran
On 7/4/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 03.07.2005 um 23:04 schrieb [EMAIL PROTECTED]:
>
> > It needs improvements i agree.
> >
> > i am on vaca! tion this week so you all decide without waiting for me.
>
> I'd suggest #ifdef USE_BYTE_RANGES undefined by default. You can
>
Am 03.07.2005 um 23:04 schrieb [EMAIL PROTECTED]:
It needs improvements i agree.
i am on vaca! tion this week so you all decide without waiting for me.
I'd suggest #ifdef USE_BYTE_RANGES undefined by default. You can
temporarily tweak the Makefile to define it.
OTOH, what Stephen is suggesti
Am 03.07.2005 um 12:27 schrieb Stephen Deasey:
I'm wondering if the best way forward is to back out the range code,
make a quick release, then add it back for the next one along with the
TclVFS stuff, file upload improvements, and hopefully my mythical
caching changes, all of which are pretty in
I was building range code to support streaming from VLC player and it does wirk. Also i have this code running on out public site and i see many range requests coming with asking partial contents so it is working in real life. The implementation is not complete but i've never seen in the logs multi
> I'm wondering if the best way forward is to back out the range code,
> make a quick release, then add it back for the next one along with the
> TclVFS stuff, file upload improvements, and hopefully my mythical
> caching changes, all of which are pretty invasive and potentially
> destabilizing. W
It doesn't make sense for the client to ask for a certain byte range
unless it already has the other bytes. It needs to make sure that
it's not asking for the tail of a file which has changed in the
server.
The code doesn't handle If-Range. If-Modified-Since is handled in the
existing code and r
