able to set autoload entries even the parameters are not correct

[hchen59]

Description:
=========
Able to set autoload entries with incorrect sink/source/module name, via API pa_context_add_autoload().

Details:
======
1> Try to add autoload sink: pa_context_add_autoload(context, sink_name, PA_AUTOLOAD_SINK, module_name, module_argv, context_index_callback, NULL) => use sink_name="fakesink", module_name="fakemodule", module_argv=NULL. Return index=0

2> Try to add autoload source: pa_context_add_autoload (context, source_name, PA_AUTOLOAD_SOURCE, module_name, module_argv, context_index_callback, NULL) =>use source_name="fakesource", module_name="fakemodule", module_argv=NULL. Return index=1

Go to list-autoload in pacmd, both upper two entries are listed. This behavior seems incorrect. At least PA should check specified module name according to module list supported.

[coling]

I'm pretty sure the autoload stuff was deprecated a while back, so it's probably not a good idea to use these methods.

See [cdfcf].

[coling]

Hmmm the link didn't work see [changeset:cdfcf]

[hchen59]

Ok, I see. autoload API wouldn't be used for future version of PA server.

I think in order to autoload modules, just modify default.pa in etc/pulse/default.pa

[coling]

Yeah if you are developing a patch then you can just edit the src/daemon/default.pa.in in your checkout.

I think (for now) Lennart would prefer that modules are developed "in tree" e.g. with the main source. That may change in future but there is currently no guarantee of the module API stability between releases (unlike the client API), so keeping all the things that are affected by a given change together keeps things easy.

In the future I'd suspect we will add support for a /etc/pulse/default.pa.d/ folder that reads all the config files within which would allow for easier out-of-tree module development. But like I say, this is not likely to happen all that soon.