- From: <ryman@ca.ibm.com>
- Date: Wed, 12 Jun 2002 03:59:10 -0400
- To: Hao He <Hao.He@thomson.com.au>
- Cc: "''www-ws-desc@w3.org' '" <www-ws-desc@w3.org>
Hao,
AKAIK, they use Apache SOAP.
Arthur Ryman, PhD
Senior Technical Staff Member
Web Services Tools Architect
phone: 905-413-3077, TL 969-3077
assistant: 905-413-2323, TL 969-2323
fax: 905-413-4920, TL 969-4920
intranet: http://w3.torolab.ibm.com/~ryman/
Hao He
<Hao.He@thomson. To: Arthur Ryman/Toronto/IBM@IBMCA
com.au> cc: "''www-ws-desc@w3.org' '" <www-ws-desc@w3.org>, "'www-ws-desc-request@w3.org
Sent by: '" <www-ws-desc-request@w3.org>
www-ws-desc-requ Subject: RE: an image processing use case for wsdl
est@w3.org
06/11/2002 11:01
AM
Please respond
to Hao He
Arthur,
Thanks for the info. Did they use a SOAP architecture or RESTful
architecture?
What I try to see is if wsdl can be used to describe a RESTful web
services.
Hao
-----Original Message-----
From: ryman@ca.ibm.com
To: Hao He
Cc: 'www-ws-desc@w3.org'; www-ws-desc-request@w3.org
Sent: 6/12/02 12:21 AM
Subject: Re: an image processing use case for wsdl
Hao,
IBM jStart did a Web services engagement with Adobe on a system called
AlterCast. AlterCast is an image processing service that has a Web
services
interface. Perhaps you could look into it to determine the solution they
adopted.
"To help their customers automate image production workflows,
Adobe is introducing Adobe AlterCast? image server. Adobe
AlterCast software automates the production process and provides
a way to innovate with images and reduce costs."
See case study:
http://www-3.ibm.com/software/ebusiness/jstart/casestudies/adobe.html
Atercast info: http://www.adobe.com/products/altercast/main.html
Arthur Ryman
Hao He
<Hao.He@thomson. To:
"'www-ws-desc@w3.org'" <www-ws-desc@w3.org>
com.au> cc:
Sent by: Subject: an image
processing use case for wsdl
www-ws-desc-requ
est@w3.org
06/11/2002 10:02
AM
Please respond
to Hao He
hi,
I mentioned some of my concerns this morning about wsdl's support of
REST.
I'd apprecite
any feedbacks on the follwing use case:
Suppose we have an image processing WS. All images are droped to this
URL:
http://www.foo.com/image/incoming, using POST.
All clients will then get processed image from the following URLs:
http://www.foo.com/image/$client_id/
after, say, 10 minutes from droping the images.
The question is, how do we use wsdl to describe this service?
Hao
(See attached file: InterScan_Disclaimer.txt)
<<InterScan_Disclaimer.txt>>
#### InterScan_Disclaimer.txt has been removed from this note on June 12
2002 by Arthur Ryman
Received on Wednesday, 12 June 2002 03:59:18 UTC