biNu XML pages are served from the remote biNu application and then executed by the biNu Server. The app's pages are not sent directly to the client. Instead the biNu Server interprets and executes the XML, and anticipates various states that can occur on the client as the user interacts with the page. Each state is encoded as an impression and definitions of the different Impressions are sent to the biNu java client on the mobile phone.
The client appears to be executing the application by moving from impression to impression or state to state. biNu achieves much of it’s efficiency by only sending impressions and not entire XML pages.
There are four types of executor:
- Fixed – content is laid out in a fixed position on the screen.
- Panning – contains scrollable content through which the user can scroll up and down.
- Listing – defines a list of repeatable rows on the screen.
- Text Entry – defines an area where the user can enter data on the screen.
The listing and panning executors can automatically update impressions with changing data using PushUpdate.
Each pageSegment can only have one executor. An executor is defined within a pageSegment and the output of the executor is displayed within the window defined by the pageSegment.