Re: [naviserver-devel] TclVFS changes done (at last!)

On 10/4/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > Hi friends, > > I have made the TclVFS changes finally, believe or or not! > > Before wholesale commit, I will however tag the current > CVS state as before-tcl-vfs (any better idea?) so you/we > can backoff if we found some serious, non-fix

[naviserver-devel] TclVFS changes done (at last!)

Hi friends, I have made the TclVFS changes finally, believe or or not! Before wholesale commit, I will however tag the current CVS state as before-tcl-vfs (any better idea?) so you/we can backoff if we found some serious, non-fixable problem. I have replaced most of the internal direct OS calls

Re: [naviserver-devel] Range: header parsing info

Am 04.10.2005 um 09:37 schrieb Zoran Vasiljevic: Hi, Vlad, you have made the ParseRange() call in the fastpath.c. Can you help me understand the "Range:" header layout? Is it something like: Range: bytes=a-b,c-d,e-f or Range: bytes=-a Or, can it only be: Range: bytes=a-b or

[naviserver-devel] Range: header parsing info

Hi, Vlad, you have made the ParseRange() call in the fastpath.c. Can you help me understand the "Range:" header layout? Is it something like: Range: bytes=a-b,c-d,e-f or Range: bytes=-a Or, can it only be: Range: bytes=a-b or Range: bytes=-a I have some trouble understanding