Trying to get familiar with the PMS HTTP/XML communication path I am playing around a little. You might have read my “Bonjour-Issue” already.
Now I am a couple of steps ahead, walking the library extensively using the “key” field.
Unfortunately this does not work everywhere… going down System->Plugins->AllPlugins->Vimeo (yes… I installed this previously the “key” somehow turns bad. Instead, a “path” tag pointing to “/video/vimeo” shows up, which apparently does the trick.
Question: How do you know, which tag to use? Why is there an exception to the "walk the keys"-rule?
Is there detailed documentation available on the usage of all those tags?
Any insights?
So, from my experience anything in system/plugins acts as a link to the actual plugins (bit like a unix sym link). So system/plugins/all is used to provide a channel like single view XML, and you then use path to move to the actual plugin.
so it’s kinda the exception rather than the rule.
EDIT: as for the tags, I just use what I need:
unique - is the plugin name unique (i.e. iTunes which a separate audio and video plugins - so add a suffix)
hasStoreServices - I assume this is whether it has been install via store or manually
thumb - thumbnail
type - what is it
serverVersion - version of service delivering plugin
title - self explanatory
host - server delivering plugin
hasPrefs - does the plugins has a prefs pane/dialog
path - URL to access the plugin
serverName - friendly Bonjour name of server with plugin
art - fanart
identifier - internal name of plugin
local - is the plugin local to the server you are viewing XML from
the “key” somehow turns bad. Instead, a “path” tag pointing to “/video/vimeo” shows up, which apparently does the trick.