RE: A different binding example (was RE: Binding)

> -----Original Message-----
> From: Edwin Khodabakchian [mailto:[email protected]]
> Sent: Monday, January 06, 2003 5:21 PM
> To: 'Champion, Mike'; [email protected]
> Subject: RE: A different binding example (was RE: Binding)
> 
> 
> 
> 
> I am happy to take a stab at it given that this use case is 
> close to the
> type of applications and flow our customers develop.

Thanks!  This is helpful.

> 
> I would create a Web Queue resource (
> https://www.collaxa.com/expensereport ). When a developer 

How critical is the Web Queue resource to the scenario?  It would be nice,
for the purposes of the WSA document, to have a "pure" REST approach
sketched out. [Not that I mind the plug for your product :-) ]

> 
> If I am not sure that the POST was received successfully, because the
> connection failed and I did not get the URL, I would POST the same
> message again. The server would use a correlation set to determine if
> the message has already been received or not.

The "correlation set" is mentioned as a bit of an afterthought.  It would be
nice if it were more closely integrated into the sketch of the solution.
Would the correlation set be, or be based on, the URI returned from the
original POST?  

> 
> The server software, implemented in perl, Java, "manual fax" would
> process the expense report asynchronously in the background. 
> When it is
> completed or if an exception occurs, it would post to the callback
> location specified in the request, the confirmation or fault XML
> document.