Re: [ws-rx] PR33 - Re: [ws-rx] NEW Issue back-channel not defined

[Christopher B Ferris <chrisfer@us.ibm.com>]

-1!

It is important that we preserve the
"without initiating a new connection" aspect.

Paul, unless you can come up with something
more specific than: "I think there may be..."
then I see no reason to relax the definition
as in this latest revision from Matt.

I would prefer we went with:

Backchannel: When the underlying transport provides
a mechanism to return 
a transport-protocol specific response without initiating
a new connection, 
we refer to this mechanism as a backchannel.

Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
phone: +1 508 377 9295

Paul Fremantle <paul@wso2.com>

12/14/2006 11:26 AM

To	Matthew Lovett <MLOVETT@uk.ibm.com>
cc	ws-rx@lists.oasis-open.org
Subject	Re: [ws-rx] PR33 - Re: [ws-rx] NEW Issue back-channel not defined

+1

Thanks!

Paul

Matthew Lovett wrote:
> OK, so how about:
>
> Add to the glossary:
> Backchannel: When the underlying transport provides a mechanism to
return 
> a transport-protocol specific response, we refer to this mechanism
as a 
> backchannel.
>
> Matt
>
> Paul Fremantle <paul@wso2.com> wrote on 13/12/2006 21:15:33:
>
>   
>> Matt
>>
>> I still don't agree that this is right. I think there may be cases
where 
>>     
>
>   
>> there is a new transport level connection. The main point is that
the 
>> response channel is transport-defined not WS-A defined.
>>
>> Paul
>>
>> Matthew Lovett wrote:
>>     
>>> Hi all,
>>>
>>> I found the last suggestion a bit cumbersome, so I has another
go. I 
>>>       
> hope 
>   
>>> people like it :)
>>>
>>> Add to the glossary:
>>> Backchannel: When the underlying transport provides a mechanism
to 
>>>       
> return 
>   
>>> a transport-protocol specific response without initiating
a new 
>>> connection, we refer to this mechanism as a backchannel.
>>>
>>> Thanks
>>>
>>> Matt
>>>
>>>
>>>
>>>       
>> -- 
>> Paul Fremantle
>> VP/Technology and Partnerships, WSO2 
>> OASIS WS-RX TC Co-chair
>>
>> http://bloglines.com/blog/paulfremantle
>> paul@wso2.com
>> (646) 290 8050
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>>
>>
>>     
>
>
>   

-- 
Paul Fremantle
VP/Technology and Partnerships, WSO2 
OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
paul@wso2.com
(646) 290 8050

"Oxygenating the Web Service Platform", www.wso2.com