W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2001

Re: AMG: New AM document snapshot 27th March 2001

From: Mark Jones <jones@research.att.com>
Date: Fri, 30 Mar 2001 07:53:39 -0500 (EST)
Message-Id: <200103301253.HAA02104@glad.research.att.com>
To: NAKAMURY@jp.ibm.com, moreau@crf.canon.fr
Cc: jones@research.att.com, skw@hplb.hpl.hp.com, xml-dist-app@w3.org
	From moreau@crf.canon.fr Fri Mar 30 02:07 EST 2001
	Delivered-To: jones@research.att.com
	X-Authentication-Warning: lancelot.crf.canon.fr: smap set sender to <moreau@crf.canon.fr> using -f
	Date: Fri, 30 Mar 2001 09:06:37 +0200
	From: "Jean-Jacques Moreau" <moreau@crf.canon.fr>
	X-Accept-Language: en,fr
	MIME-Version: 1.0
	To: Yuhichi Nakamura <NAKAMURY@jp.ibm.com>
	Cc: xml-dist-app@w3.org, Mark Jones <jones@research.att.com>,
	        "Williams Stuart" <skw@hplb.hpl.hp.com>
	Subject: Re: AMG: New AM document snapshot 27th March 2001
	Content-Transfer-Encoding: 7bit

	Yuhichi Nakamura wrote:

	> [...]
	> I suspect that this document [the AM]
	> describes block cosuming, but not block producing clearly.
	> Am I right?

	I think you are right, there is little said in the AM about block
	producing, apart that, once created, they are transmitted using the
	XMLP_UnitData.send primitive. Now, what else is there to say?

	Jean-Jacques.

One thing to say is where the blocks go in the message.  There may be
order dependencies among them.

If there is a header/body distinction, then one would have to say
whether they were header or body blocks.

For blocks that are to be returned as a part of a response message,
you have the same issues.

--mark

Mark Jones
AT&T Labs
Received on Friday, 30 March 2001 07:53:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:00 GMT