WhiteFrost

I've made a general site upgrade to dogfood a major revision to Engine for Web Applications, code named Hemi. Hemi is a JavaScript Web Framework for AJAX, Monitoring (Analytics), service-oriented portal development, and HTML templating and code-behind.

I added promotional branding to older projects, such as libXmlRequest as well as Engine to raise awareness of the new version.

I'm excited with how "Hemi" has turned out. I still need to extricate a number of hooks to the older Engine framework.

Engine 2.0 and Account Manager 4 were updated to include support for Distributed Web Application Components Anonymous use is coming soon. In the meantime, registered users can access the /DWAC/ builder as /DWAC/{username}. For example, my builder is located at /DWAC/steve/.

The DWAC Builder bundles together several development tools for Engine.

DWAC Explorer

The DWAC Explorer provides a launch point for the Profiler, API Browser, and for browsing Components, Templates, Fragments, and DWAC Bundles.

Builders

At present, there are three types of builders: Template Builder, Fragment Builder, and Component Builder. The DWAC Bundle tool is coming soon. Each builder includes New, Save, and Delete functionality handled by the Account Manager 4 DWAC Handler, and the special Running feature to test the code, alongside with example HTML and Script to show how to re-use the tested component on your own Web page.

1. Component Builder - Quickly create Application Components with a number of demonstration variations.
2. Template Builder - Templates are a means to quickly display and change user interface elements via Application Componnets, and make it very easy to manage Virtual Forms. The Template Builder includes a few demonstration variations and a feature to link in fragments.
3. Fragment Builder - Fragments are reusable XHTML and embedded script sections.

Running Feature

After developers create their Component, Template, or Fragment, they can test it immediately by running it in an on-demand Running engine. The active object can be sent to the inline Active Source tool to make queries against the live object. If the Engine Profiler is open before the component is run, the profiler results can be filtered to only show the actively used Engine objects.

Engine Profiler

The Engine Profiler is an inline development tool for working with Engine, and includes a number of helpful features. Try the Engine Profiler.

1. Running Engine Stats - browse through the current in-memory objects and statistics of Engines, Tasks, Transactions, Application and XHTML Components.
2. Active Source - This is an inline version of the Active Source tool available as part of the JavaScript Profiler.
3. Script Profiler - This is an inline version of the Script Profiler tool available as part of the JavaScript Profiler.
4. XML/XSL Tool - This is the same inline tool used for the XSL Primer document.

API Browser

The API Browser is an inline documentation browsing tool for quickly looking up the core Engine API. Try the API Browser.

Engine 2.0, libXmlRequest, Account Manager 4 and the site were updated.

Engine for Web Applications (v 2.0)

Engine for Web Applications 2.0 was updated to resolve DOMStorage support for Internet Explorer 8, and include additional JSON support features.

libXmlRequest (v. SPEC-2.0.1.0226.2009)

libXmlRequest was updated to include additional helpers for working with JSON objects.

Account Manager 4

Account Manager 4 Beta 2 was updated to enhance the Handler classes. Handlers are REST implementations of Account Manager 4, and front the Blog/, Media/, Forum/, and DWAC/ tools. The new implementation isn't as clean as I'd like, but the handlers now follow a more consistent URI structure.

Security policies are now better enforced through a new AuthorizationUtil class. The longer term objective is a general policy wrapper (or an internal XACML representation).

Monitoring

The Core Monitor projects are included with the Account Manager 4 / Core Web bundle. The monitors include passive performance, behavior, and interaction client monitors derived from the Engine monitor service. The database schemas, receiver and aggregator, and SVG report library (note: the IMNMotion report browser UI isn't included yet) for the performance and behavior monitors are provided. The Interaction monitor is still a prototype.

A project page will be created to provide instructions on setup and use.

Engine 2.0 and the site were updated.

Engine for Web Applications (v 2.0)

Engine for Web Applications 2.0 is now available.

Account Manager 4

Account Manager 4 Beta 2 is now available.

Engine and the site were updated.

Engine for Web Applications (v 1.9.6)

Version 1.9.6 includes a number of procedural updates in anticipation of version 2.

Version 2 will include the groundwork for Distributed Web Application Components (DWAC), something that I've been working on for a while. DWAC is similar to gears and gadgets in that they encapsulate a product, but different in that they are meant to run as a self-contained distribution (framework being made available, of course). Most important is the existing features of engine, particularly application components and templates, make it very easy to build out new DWACs.

Other V2 features: A specific section for monitoring, including performance, behavior (aka: IMNMotion), and customer monitors.

Web Site

Some style changes were made to improve browsing experience.

Account Manager 4 and Core Web were updated.

Account Manager 4

Account Manager 4 was updated to include spool and ticket factories, as well as degraded pagination for non-rich lists to facilitate better robot discovery.

Core Web

Core Web uses the spool and ticket factories to provide basic protection against cross-site request forgery (CSRF) requests. The implementation is included in the SecurityToken control. Static content pages that use the session gizmo will automatically register for the ticket. The intent is to establish contextual residency for a session prior to allowing an particular action.

Pages inheriting from the CorePage class can validate against a submitted ticket before continuing. Tickets may be general purpose, or may be restricted to specific URIs.

Some style changes were made to improve browsing experience, and to alter the window gizmos.

JavaScript Profiler 2.0 was updated to include better detection of embedded functions typical of libraries and frameworks.

JavaScript Profiler 2.0 is available for download (JavaScriptProfiler.zip). Version 2.0 includes integrated support for Function Monitor and the latest version of Active Source.

JavaScript Profiler is a context menu extension for Internet Explorer, and is useful for exploring the live DOM and profiling JavaScript functions.

Account Manager 4-B1 is available for download (AccountManager4.zip - Source - 1.3MB). The download includes the Core Web project, and Vault 2 reference implementation. API Documentation is also provided online (built with Doxygen).

Please Note: This is a BETA. Some of the features are not complete.

• Page controls were updated to use links.
• Account Manager 4Account Tags and Account Roles configuration added to administration dialog.
• Raw HTML no longer permitted in Blog and Forum articles. A BB style syntax may now be used.
• Changing password via Web UI now requires confirmation of existing password to prevent scripted attacks.
• Failed login attempts are now blocked for the session and/or ip address.