RE: [Widex] Proposed rewording for Framework draft

>    The Widex Framework needs a mechanism by which the Widex Renderer
>    determines which events have a remote scope and therefore need to be
>    serialized and forwarded to the Widex Server.  The determination of
>    which events have a remote scope could be achieved in one of three
>    ways:
> 
>    o  prior agreement between the Widex Renderer and Widex Server
>    o  a list of events passed during session establishment
>    o  the Widex Server could direct the Widex Renderer to add and remove
>       event listeners during the session

For the second bullet, I prefer "a list of messages..." rather than "a list of
events...". The word "event" is overloaded here; I don't think it refers to "UI
event", which is used predominantly in rest of the text.

>    In an implementation where the Widex Server maintains an explicit XML
>    DOM for the View, changes made by the Widex Server to this View
>    result in DOM events, e.g.  DOM Mutation events.  The Widex Framework
>    in the server (as shown in Figure 1) can listen for these events to
>    generate the corresponding Widex messages.  The Widex Framework in
>    the Renderer interprets these messages to reflect the changes to its
>    copy of the XML DOM for the View.  Note that the Widex messages are
>    independent of whether the Widex Server has an explicit or a virtual
>    View, that is, an in-memory XML DOM tree, as this is an
>    implementation dependent design choice.

Perhaps we can rephrase the last sentence as:

"Note that the Widex messages are independent of whether the Widex Server
maintains an explicit DOM for the View, that is, an in-memory XML DOM tree, as
this is an implementation dependent design choice."

Regards,

Jin
________________________________________
Jin Yu
OpenXUP.org

_______________________________________________
Widex mailing list
Widex@ietf.org
https://www1.ietf.org/mailman/listinfo/widex