byterange support in http access
-> drop adaptive internal http
We need a way to support byterange parameters in access. Either:
- custom internal scheme containing range parameters & original scheme ex: http(s)range-N-N://
- new streamUrl API parameters
- or variable on parent object before StreamUrlNew()