Improve the websockets demo so that the websocket is not started on page load.
This makes it easier to look at packets that are exchanged, without reloading
the full javascript each time. Also change javascript so that new status do
not replace the message on the page, but add to it (so that we can see "open"
and "close", not just "close" for instance)
L629-010
* po/update-prototype:
Add proper XML header to web_elements demo.
Update to prototype.js v1.7
* po/websockets:
Add overriding as keyword to highlight into the spec.
Integrate WebSocket into AWS.
Add WebSocket implementation following RFC-6455.
Add Sec_WebSocket_Origin_Token, check this token in Messages.Origin.
Add new response for WebSocket.
Add new config parameter WebSocket_Origin.
Add support for regular expressions in AWS.Config.
Add new config parameter WebSocket_Message_Queue_Size.
Add new config parameter Max_WebSocket_Handler.
Add support for WebSocket headers/messages.
Use private with instead of standard with clauses.
Remove superfluous use type.
Minor reformatting.
AWS now provides an ajax_api.tjs file containing macros to do Ajax
development. This is cleaner than using include file. The two
Ajax demos have been rewritten to use this new feature.
Update the documentation accordingly.
--
For J706-026.
This new implementation separate the context from the session handling.
This new context is now content based. A context id depends on the
content in the context. Each page generated will have a different context
id if the context has been updated.
This fix a serious problem with the browser's tab or back button which
could corrupt an application by using a wrong context.
--
Work for I804-012.
To be able to add a set of Ajax actions into a TABLE
statement we need to be able to specify unique JavaScript
id/name. For this a new parameter has been added to be
able to pass an ID_INDEX (as parameter 18). For example
this parameter can be passed the @_TABLE_LINE_@ tag.
When the user open a link in a webpage in a new tab, the original tab
had is context modified. To avoid this, we should keep the old context
and revert the last changes when a new tab creation is detected.
At the same time aws_kernel.tjs has been updated
to properly work with this new version. A change
in the way the serialize routine was implemented in
the new framework was causing problem.
a simple elment under a specific name. This is needed
to better control the name used on the Ada side and
unrelated to the naming convention in the template.
is the derived absolute URL. So to detect local URL we look at the
hostname if URL is prefixed by "http:".
Check for null id for the replace action.
Minor reformatting.
Update Web_Block framework to properly order the translations
table update. The last update is now done by the user's callback.
* web_elements/javascripts/aws_kernel.tjs:
Update framework to support per-windows context.
- The HTTP validate.
- The AWS runtime is not loaded in every pages.
- The framework has been clean-up to use a more
"object oriented" implementation. The global namespace
is not polluted anymore.
There is no end-user visible changes.
Work for G215-018.