Http classes not easily extendable about exoplayer HOT 3 CLOSED

• You should IMO consider DataSource as the common interface that you can plug an arbitrary network stack into. I see little value in defining a more specific HttpInterface under HttpDataSource. You'd likely end up writing nearly as much code adapting an arbitrary network stack onto this interface as you would mapping it onto DataSource directly.
• I want ManifestFetcher to use DataSource in order to fetch manifests, which would allow your single whatever-network-stack-you-want-DataSource implementation to be used in both places. Right now the DataSource interface doesn't allow querying of content type, which appears to be needed when retrieving manifests. I need to look into that a little bit and see if there are any other implications, but it's probably possible to get that resolved and move over to this way of doing things.

from exoplayer.

So to clarify, I propose using this bug to track having ManifestFetcher use a DataSource.

from exoplayer.

Okay thanks, looking forward to this.
edit: I just saw in the dev guide where you suggest extending DataSource for a custom network stack. My bad :)

from exoplayer.