xpcom

. Therefore, the next-generation application platform should have the permission to access local computing resources. Better integrate local resources. This is related to the above. The difference is that it will allow network applications to access local disks, configurations, registry files, and so on. Better security mechanisms. Without a doubt, all applications run through ActiveX and XPCOM, but the security mechanism is a weakness, and it i

the preferred language for developing efficient systems. Therefore, we need to use C ++ to implement the plug-in mechanism. In many cases, this is something we cannot bypass.Is there any solution? Before developing our new plug-in framework, we 'd better take a look at the existing library or framework. Currently, there are both heavyweight solutions, such as Microsoft's com and Mozilla's XPCOM (cross-platform com), and they only provide basic functi

operations on its browser interface and its interface are completed by JS and XUL, this is the power of ff, and it also provides a good extension mechanism for everyone. FF extended development directory structure: -- Content -- [Main JS XUL files] -- Locale -- En-US -- [Some DTD or properties files] -- [Other ages] -- Skin -- [Some CSS files or pictures] -- Defaults -- Preferences -- Components [Optional] -- Chrome. manifest -- Install. RDF -- Install. js [Optional] FF working method: For a

SATA raw disks andpartitions USB support, with remote devices over RDP Snapshots Seamless mode Clipboard Shared folders Special drivers and utilities to facilitateswitching between systems Command Line Interaction (in addition to Thegui) Public APIs (Java, Python, SOAP, XPCOM) tocontrol VM configuration and execution [10] Remote display (useful for headless hostmachines) Nested Paging for Amd-v VMware Virtual Machine Disk Format (VMDK) sup

Explorer, or Jav Ascript engine and Firefox's XPCOM infrastructure). Here are some rules of thumb to avoid memory leaks: Use an event system to attach an event handler function The most common circular reference mode [DOM element--> event handler--> closure Scope--> DOM] is discussed in this MSDN blog article. To avoid this problem, you can use a rigorously tested event system to attach event-handling functions such as Google doctype, Dojo, or JQu

performance because it modifies the scope chain, making it expensive to find variables in other scopes. Avoid browser memory leaks Memory leaks are a common problem for WEB applications, which can cause serious performance problems. When the browser's memory usage goes up, your Web application, along with other parts of the user's system, slows down. The most common memory leaks for WEB applications are the circular references between the JavaScript scripting engine and the C + + object imple