Serving media from non-local/dummy filesystem

[kksharma1618]

Serving media from non-local/dummy filesystem

[kksharma1618]

@anacrolix
Thanks. Still not sure which route we want to go with. Currently we are using fuse api to mount our structure as a folder, and using dms on top of it. Don't know how stable that is especially on windows.

[kksharma1618]

@anacrolix
Regarding your previous comment "and allow for replacing or adding new locations"
I was checking your ./dlna/dms/cd-service-desc.go file.
You are specifying actions like CreateObject, DestroyObject, UpdateObject, MoveObject, ImportResource. But I dont see any implementation for them in the code. If we develop an interface, would it have to support those features.

[anacrolix]

This would be a welcomed feature. You would need to distil the current filesystem related stuff as an interface to provide for abstracting out the current stuff, and allow for replacing or adding new locations.

[anacrolix]

We can use this issue to track the interface we described?

[kksharma1618]

Sure. actually I have a working fork at https://github.com/kksharma1618/dms
master...kksharma1618:master
Which is good enough for our particular use. Instead of adding interface, I just added an argument "-contentProviderServer". I am providing url to our own backend there.
Then in dlna/dms/cds_server.go file, I am pulling content from that api.
That apis provides folders/items data as contentProviderServerItem struct. Which I transform into upnp.Object in Browse action.
That api also provides icon/media url. dms just proxies it.

Basically, "contentProviderServer" provides api endpoint with:
/browse?id={objectid}
-- gives array of children for root -> []contentProviderServerItem{}
-- item for media has thumbnail/media url set.

dms proxies thumbnail/media content from the provided url (I dont want to open up my app server on 0.0.0.0)
(dms.go serveCdpProxy)

I am not that familiar with golang, so code is probably pretty bad. But atleast works for our custom case.

[anacrolix]

It looks best if you keep that code for your custom case.