Architecture

Nexaweb Client Architecture

Nexaweb client architecture consists of: 

1. XML Parser and Namespace handler:

   The XML parser is responsible for parsing the input XML and calling the appropriate namespace.  Input XML consists of User Interface, modification instructions (XUpdate or XModify), remote inclusions (XInclude), Data Binding or Data Services declarations or Macro and MCO declarations. 

2. System containers that manage different namespaces:

   The system container manager handlers for namespaces such as MCO, Macro, XInclude and XModify/XUpdate. 

3. The User Interface DOM:

   User interface state is managed by the UI DOM. 

4. User Interface Components and Component Bridges:

   Each UI tag maps to a user interface component and component bridge.  The user interface component is a Nexaweb provided widget implementation that renders the object to the screen.  The bridge maps the visual component to the XML tag including attributes and eventing.  Using the Plugin Architecture, developers can create their own mapping. 

5. APIs:

   Nexaweb provides server APIs listed below.

Nexaweb Workflow
 

Highlights

1. XML Parser processes the starting XML and each subsequent XML
2. Namespace handlers provide functionality based on the namespace of the XML
3. The UI DOM manages application UI state and can be incrementally updated
4. Component bridges map XML tags to UI components; user interaction with the user interface results in events

The developer interaction occurs through (A) providing XML and (B) the API interfaces.

Available APIs

1. DOM API:

   Provides direct access to the UI and other DOMs. 

2. System Services:

   APIs to access Network, Display, Sound and other services provided by the Nexaweb system.  For detailed API documentation visit API documentation. 

3. NFC:

   Type safe wrappers around the DOM APIs.