MHonArc v2.5.0b2 -->
















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Manifest -> PayloadInfo thoughts.




From: Matthew MacKenzie <mattm@adobe.com>
To: Jeff Turpin <jturpin@cyclonecommerce.com>
Date: Wed, 02 Jun 2004 15:20:00 -0400






So, now we have:

<Manifest>
	<Reference id="cid:foo"; xlink:type"simple" xlink:href="cid:foo"; 
xlink:role="">
		<Schema location="http://foo/bar.xsd"; version="1.0" />
		<Description>
			...
		</Description>
	</Reference>
</Manifest>

I am thinking:

<PayloadInfo>
	<Payload id="cid:foo | #idref" schemaLocation="href" schemaVersion="1" 
...>
		<Description />
		<PreProcessing>
			<Step sequence="0" id="urn:foo:ps:CompressionSvc">
				 <Parameter name="command" value="compress" />
         				<Parameter name="algorithm" value="gzip" />
         				<Parameter name="gzip-level" value="9" />
			</Step>
		</PreProcessing>
		<PostProcessing>
			<Step sequence="0" id="urn:foo:ps:CompressionSvc">
				 <Parameter name="command" value="uncompress" />
         				<Parameter name="algorithm" value="gzip" />
			</Step>
		</PostProcessing>
	</Payload>
</PayloadInfo>

I would probably also come up with a new name for payload services, to 
make it sound more like a "filter" facility.
___________________________
Matthew MacKenzie
Senior Architect
IDBU Server Solutions
Adobe Systems Canada Inc.
http://www.adobe.com/products/server/
mattm@adobe.com
+1 (506) 871.5409














[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]