tag | attribute | characteristic | style | ||
new html-keywords | line | aling | point | default | |
values of new html-keywords | side | romb | |||
old html-keywords | td | id | list | ||
values of old html-keywords | circle | ||||
communication xml | sound | sync | power | ||
values of communication xml | nouser | ||||
keyboard and mouser command | enter |
Browser sends XML-message about changes, which have occurred in a document, to a server. It's reasonable to make interaction symmetric: server sends XML-commands to browser (each browser window is a separate process) to make some changes.
Input-output card, when a signal from any equipment comes to it, timer or something else can send such XML-text. Easier speaking, it's necessary for monitoring.
Presence of tag r in document header
If user kills a program-browser or loads other document into it, then browser notifies service, that blocks for updating should not be sent further, and sends the following message to service.
All commands, which server can send to a browser, are name as initiatives. Initiatives are divided into actions (column "module") and rotations.
Browser executes initiatives consistently. It executes initiatives simultaneously, which are inside tags <<>> and <</>>, and it will not begin to execute them, until it will receive closing tag <</>> It execute consistently such initiatives inside simultaneous part of execution, which are inside tags <> and </>
r |
html60author