- From: Mark Baker <mark.baker@canada.sun.com>
- Date: Thu, 25 Jan 2001 15:37:40 -0500
- To: xml-dist-app@w3.org
Greetings, Here's my comments on the strawman; - I'd like to see the synchronicity between client & server in this architecture leveraged in this document. In particular, I'd like to see what is described as an "XP Client" to be considered an XP processor that terminates. i.e. XP processors process XP messages - some XP processors pass along their messages to another processor, others don't. - re diagram in section 2 and subsequent question about layering, I'd like to see 2 layers only; an XP layer with intermediaries and terminating processors, and a "transport" layer with "transport" intermediaries. - would like to see notation synchronized with Henrik's (private, it appears) glossary submission (and vice-versa, if necessary) - unclear why an SAP - an implementation construct that isn't part of any interface - needs to be identified in an abstract model - also unclear on the value of such a complex model as described in sections 3.[123] at this time. This much detail extracted from a set of requirements is likely going to be found brittle later. 3.4 is fine, but the bulk of it might better be described as "message transfer metadata".
Received on Thursday, 25 January 2001 15:38:02 UTC