From 335d9af8dc4b02f8ec4017d30525a65e93c40eb2 Mon Sep 17 00:00:00 2001 From: zotlabs Date: Tue, 17 Jan 2017 00:14:47 -0800 Subject: daemon_addon hook - lets plugins create custom background processes. --- doc/hook/daemon_addon.bb | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/hook/daemon_addon.bb (limited to 'doc/hook/daemon_addon.bb') diff --git a/doc/hook/daemon_addon.bb b/doc/hook/daemon_addon.bb new file mode 100644 index 000000000..b60b25748 --- /dev/null +++ b/doc/hook/daemon_addon.bb @@ -0,0 +1,15 @@ +[h2]daemon_addon[/h2] + + +A foreground plugin can create a background process by invoking: + +[code] +\Zotlabs\Daemon\Master::Summon([ 'Addon', 'myplugin', 'something' ]); +[/code] + +This starts up a background process (called 'Addon') specifically for addons to use. + +Then if your plugin is also catching the daemon_addon hook that handler will be called with the +argv array of the background process. In this case [ 'myplugin', 'something' ]; + +We recommend using this convention so that plugins can share this hook without causing conflicts; that is check to see if your plugin is the first array argument and if not, return from the hook. Otherwise you can initiate background processing. Something to remember is that during background processes there is no session. You are detached from the web page which created the background process. \ No newline at end of file -- cgit v1.2.3