cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glynn, Eoghan" <eoghan.gl...@iona.com>
Subject RE: HTTP dependency/decoupling issue
Date Tue, 06 Feb 2007 00:51:49 GMT
 

> -----Original Message-----
> From: Dan Diephouse [mailto:dan@envoisolutions.com] 
> Sent: 05 February 2007 19:53
> To: cxf-dev@incubator.apache.org
> Subject: Re: HTTP dependency/decoupling issue
> 
[snip]
> just give transports a chance to customize 
> messages if they need to via a PartialResponseSupport 
> interface or the like.

Something like say AbstractDestination.markPartialResponse()?

Destination implementations override this method if they support
decoupled semantics and need to customize a partial response message
(e.g. by setting the response code to 202). 

Otherwise the Destination impl doesn't need to worry about partial
responses at all.

/Eoghan

Mime
View raw message