| [aperi-dev] launching individual, context-based functionality via URL instead of RPC plug-ins? |
|
Hi All, Has anyone on the project thought about a slightly different
plug-in model for Aperi, along the following lines? Say a vendor is
planning to write an Element Manager that can be served off of their device to
a browser via an embedded web server. The EM supports a number of
functions that are vendor unique, (e.g., get device statistics, run
diagnostics, etc.) for which it might be nice to have Aperi plug-ins.
What if those functions were exposed as individual URLs that could be launched
in context from Aperi (versus having just a single URL for the EM “main
page”)? This provides a way to have a somewhat “deeper”
level of integration with Aperi without having to write the vendor unique functions
twice (once for the Element Manager browser-based environment and once for the
Aperi runtime environment). One drawback is that it is not as seamless as
the regular Aperi plug-in mechanism. Is this feasible with Aperi?
Would it work? Thanks, Jenny Jenny Monesson, Ph.D. Solutions Architecture LSI - Engenio Storage Group, Austin TX Voice: (512) 794-3723 Fax: (512) 794-3702 |