Argonaut should ease client extension
Hello,
Right now, if someone want to extend argonaut-client-management he have to modify ClientDaemon.pm. argonaut-client-management should allow for other class to handle call. There are two ways of doing this:
- Just load several object as handler of the rpc calls, the server will search for the object that have the right method. "class.method" syntax can be used to aim a specific class
- Associate objects to paths, that's a bit more complicated to handle on the supportDaemon part, because it will need to call http://ip/greatPlugin instead of http://ip when calling RPC method, while the first choice does not require any modification on the supportDaemon side.
The other question is how does argonaut-client-management knows which object to load? A specific argonaut client module folder? A config file? And LDAP entry?
(from redmine: issue id 1016, created on 2012-06-06, closed on 2012-10-09)
- Changesets:
- Revision 8e00482e by Benoit MORTIER on 2012-06-07T08:30:51.000Z:
Fixes: #1016 Argonaut should ease client extension
- Revision 4e14d205 by Benoit MORTIER on 2012-06-07T10:41:43.000Z:
Fixes: #1016 Argonaut should ease client extension