Opened 8 years ago

Last modified 7 years ago

#212 new enhancement

there should be a way to call a plugin to return a PLE

Reported by: ph3-der-loewe Owned by:
Priority: wishlist Milestone:
Component: RoarAudio PlayList Daemon Version: current
Keywords: Cc:
Architecture: Compiler:
Difficulty: normal Kernel:
Operating System: Parent Tickets:
Patch attached: no Protocol:
Sound driver: Topic: New feature


there should be a way to call a plugin to return a PLE. This is also useful with pointers to fill a queue from an external source.

Subtickets (add)

Change History (6)

comment:1 Changed 8 years ago by ph3-der-loewe

This should be added after #198 was closed.

comment:2 Changed 7 years ago by ph3-der-loewe

beside restoring the plugin context, is there any more data needed to be passed to the plugin? like additional arguments or something like that?

What shall be the syntax?:
plugin:$registered_name or plugin:$registered_name,args... or something like that?

comment:3 Changed 7 years ago by ph3-der-loewe

  • Keywords ph3_sj added

comment:4 Changed 7 years ago by ph3-der-loewe

  • Keywords ph3_sj removed

removed keyword as it doesn't seem to be needed for this project.

comment:5 Changed 7 years ago by stephanj

the syntax which supports adding arguments seems ok:


This would allow for one plugin to be used for different purposes f.e. a db backed importer, one entry runs against a db where users could submit entries and one against a autodj instance with resampled music/entries.

comment:6 Changed 7 years ago by ph3-der-loewe

I guess arguments should follow normal roardl syntax (kv array). They should stored as array within rpld so we do not need to re-parse them every time the handler is called and we can more easily generated them via different parsers or by other plugins. if a plugin requires a persistent state (e.g. a DB connection) it should open that early (e.g. via AppSched?) and only the instance name should be passed, maybe along with simple query parameters like the queue name to select the right subset of data from the backend.

Note: See TracTickets for help on using tickets.