[vlc-devel] [PATCH] lua: http: Expose renderers

[Pierre Ynard]

> > It seems rather weird to store state inside a module.

To be clear, I meant inside the httprequests.lua module, which is just a
bunch of processing utilities loaded by each request handler. http.lua
sets up plenty of stuff, but if I understand the architecture correctly,
none that is specific to the contents of share/lua/http/; I guess that
would be what custom.lua is for.

> Fair enough, I suppose I could split the renderers listing to a
> different request, or explicitly require the user to enable renderer
> discovery instead of doing it automatically.

Automatically enabling renderer discovery at startup so it's always
available and populated is also an option, but I don't know if always
having it on is what people want. It also depends on the UX, since I'm
guessing the goal would be to set up streaming to a renderer using the
HTTP interface.

Can you please explain why it wouldn't matter which of the several RD
modules gets loaded, though?

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."