Bug 404901 - Make Extvar more decoupled from the Agent when compiling business libraries
Summary: Make Extvar more decoupled from the Agent when compiling business libraries
Status: RESOLVED FIXED
Alias: None
Product: Mihini
Classification: IoT
Component: Agent (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 0.9 M1   Edit
Assignee: Romain Perier CLA
QA Contact: Robert Jacolin CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-04 09:50 EDT by Robert Jacolin CLA
Modified: 2013-05-22 10:57 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Jacolin CLA 2013-04-04 09:50:52 EDT 
Today, in typical use case, customers have to create two shared libraries in order to extend the tree.
One that is compiling in the Customer source tree and provide access to their business logic, one that is a Lua module, and is required to be compiled into Agent source tree.

This is really not convenient and not ressource wise either (2 shared lib for 1 extension).

This idea would be to create a single Extvar handler as a Lua module. this module would use dlopen posix APIs in order to directly load each customer business libraries.
With that model we require one Lua Module + 1 shared library per extension.

The best benefit is that the customer can compile the business library in its own source tree, and then drop it into the Agent runtime along with the map file and make it run! No need any recompilation in the Agent source tree.