This content has been marked as final. Show 5 replies
It's difficult to address (1) without knowing (a) how you are measuring memory use and (b) which application you're running. However, the amount of memory used is generally a function of the application itself, not AIR.
Thanks for the response Oliver.
As for the memory footprint, I was gauging based on the Windows Task Manager, and running the EBay Desktop Air application. It’s not quite fair to judge the memory usage on that particular application since is quite complex. But it still seems high. When I started the program first, it seemed to climb as high as 20 megs, then after about 30 minutes of moderate use it reduced to 11 megs.
There is no way to call a DLL directly from within an AIR application.
Is there a way to call AIR directly from outside then? Or would it have to be through some localhost port networking communication?
My app needs to connect to some device drivers and since those APIs are not in ActionScript but in C++, I have no choice but to use C++ and ActiveX to embed the flash player. Of course this breaks the entire concept of portability since I can't do this on Mac or Linux, even if I keep the C++ platform independent.
Adobe has to address this issue and enable a Java JNI style mechanism to allow communication with other run times.