Facets of Hemi are used in a number of products and solo libraries, including JavaScript Profiler and libXmlRequest. The architecture has morphed over the last decade, though still includes many unique facets from the decade-old origins in the original MDI Framework. Starting around the year 2000, functional architectural aspects of Hemi centered on monitoring. In 2004, I wrote an article describing behavioral trends by content type: Content Under Consternation. And, in 2005, an article on using Web 2.0 for rich client-side behavior linked to backend processing: ASP.NET - Code In Front
The now defunct IMNMotion Behavior Monitor product, both the monitor and portal, drove the foundation of Hemi JavaScript Framework (at the time, Engine for Web Applications). As mentioned in the Web Page Monitoring article, the function of a framework is both availability and invisibility. Most users don't care what's going on behind a Web page so long as it doesn't break. Therefore, most enterprises are (or should be) concerned that any third party scripts they put on their Web site doesn't impact user experience.
Hemi (and Engine) deployments have operated without error or user impact in many enterprise organizations from as early as 2003.
[ Stephen W. Cote, 2011 - BSD ]