Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hey gang. I have a question about writing an extension to enable communication between multiple applets. My first thought was to have an extension (we'll call it ExtComm) which can have expose an API that has the ability to set and get data (EXTCOMM_Set(...) & EXTCOMM_Get(...)). A publisher app, AppPub, could call EXTCOMM_Set(...) and the extension could store the passed in param on the fs by doing an IFILE_Write to a file that is known only to the extension. A reader app, AppRead, could call EXTCOMM_Get(...) to read the extension's file and return the resulting data.

Here's where I have a bit of a problem, by default, when the publisher app, AppPub, uses the extension, it's namespace is rooted it its home dir (/mod/apppub). So, now we have an access problem if the reader, AppRead, tries to IFILEMGR_Open the file because now the file path is rooted in the reader's home dir (/mod/appread).

Any suggestions? Examples would be most helpful. Is there a better way to do this?

Thanks in advance!

Extension runs in the context of loader application.
In pre 3x BREW, that mean your file writer extension was able to write data only in the loader application folder, from BREW 3.x onwards, you could possibly set the ACL for the extension. Please note that it is possible that ACL for extension could be same as ACL for the loader application, I haven't verified it. You possibly need to check it.

Extension runs in the context of loader application.
In pre 3x BREW, that mean your file writer extension was able to write data only in the loader application folder, from BREW 3.x onwards, you could possibly set the ACL for the extension. Please note that it is possible that ACL for extension could be same as ACL for the loader application, I haven't verified it. You possibly need to check it.