You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is out of scope for fcurl or not, but I figured it was worth asking.
Is there any plan to provide an fseek analogue, providing range request support, perhaps? (e.g. fseek to an offset N and read X bytes yields a N to N+X range request). It may be too compilcated to be worth in in this wrapper.
This would also allow fcurl to be registered with fopencookie or funopen, or various libraries which take such callbacks.
Hopefully that made some semblance of sense.
Also apologies if a GitHub issue is not the appropriate place to put this; It wasn't clear from the README if there was a separate mailing list or bug tracker.
The text was updated successfully, but these errors were encountered:
Good question, thanks! I think an fseek equivalent will be really useful and almost required to provide a good "emulation" for the f family of functions. It could possibly be a bit hard to make it work in some situations but we should at least make a best effort.
I think the github issues is a sensible place to take these things, at least to start with. There's no dedicated mailing list or anything for fcurl (yet).
I added a few more functions to the README so they won't be forgotten.
I'm not sure if this is out of scope for fcurl or not, but I figured it was worth asking.
Is there any plan to provide an
fseek
analogue, providing range request support, perhaps? (e.g. fseek to an offsetN
and readX
bytes yields aN
toN+X
range request). It may be too compilcated to be worth in in this wrapper.This would also allow fcurl to be registered with
fopencookie
orfunopen
, or various libraries which take such callbacks.Hopefully that made some semblance of sense.
Also apologies if a GitHub issue is not the appropriate place to put this; It wasn't clear from the README if there was a separate mailing list or bug tracker.
The text was updated successfully, but these errors were encountered: