RE: [Widex] Proposed rewording for Framework draft

<Vlad.Stirbu@nokia.com> Fri, 16 June 2006 08:57 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrA9M-0000qy-94; Fri, 16 Jun 2006 04:57:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrA9L-0000qs-3C for widex@ietf.org; Fri, 16 Jun 2006 04:57:55 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrA9J-0005RC-KJ for widex@ietf.org; Fri, 16 Jun 2006 04:57:55 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k5G8vpff026753; Fri, 16 Jun 2006 11:57:52 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Jun 2006 11:57:12 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Jun 2006 11:57:11 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Widex] Proposed rewording for Framework draft
Date: Fri, 16 Jun 2006 11:57:04 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268BA0E80E@trebe101.NOE.Nokia.com>
In-Reply-To: <000801c690f0$501e6d80$0202fea9@martsbs.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Widex] Proposed rewording for Framework draft
Thread-Index: AcaQWN+gIku4mVYuTwG/pUcVvlxUqQAjiiSwAA7XHqA=
From: Vlad.Stirbu@nokia.com
To: jyu@openxup.org, dsr@w3.org
X-OriginalArrivalTime: 16 Jun 2006 08:57:11.0438 (UTC) FILETIME=[DAEAE2E0:01C69122]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: widex@ietf.org
X-BeenThere: widex@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working list for the WIDEX working group at IETF <widex.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/widex>
List-Post: <mailto:widex@ietf.org>
List-Help: <mailto:widex-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/widex>, <mailto:widex-request@ietf.org?subject=subscribe>
Errors-To: widex-bounces@ietf.org

Hi Jin, 

>
>> >>   In a little more detail, changes made by the Widex Server
>> >>   to the XML DOM for the 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.
>> >

>
>I think we could just rephrase your paragraph a bit, implying 
>it's a possible implementation approach. Also, I don't quite 
>understand the last sentence - what do you mean by "explicit 
>view"? My understanding is that the server's view is always 
>virtual, whereas the renderer keeps the concrete (or physical) view.
>
>Regards,
>
>Jin
>________________________________________
>Jin Yu
>OpenXUP.org

The "explicit view" on the Widex Server is when the UI exported through
Widex is of a desktop application, case in which a physical view is kept
also on the Widex Server.

Vlad 

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