OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ws-rx] Minimalist GetMessage proposal


I must say the proposal is much improved and scoped.
It of course works only with offered sequences - I am still trying to
convince myself that not being able to poll for CS is not a (serious)
issue. 
A wild idea: the unreliable-in/reliable-out case could be handled better
by allowing an wsrm:Offer on the GetMessage... 

Jacques 

-----Original Message-----
From: Paul Fremantle [mailto:paul@wso2.com] 
Sent: Wednesday, May 03, 2006 12:05 PM
To: wsrx
Subject: [ws-rx] Minimalist GetMessage proposal

Based on some of the discussions it seemed to me that it could be 
valuable to produce a completely "minimalist" GetMessage proposal.

This is a new proposal that is based on the previous WSO2 proposal.

The proposal removes the MessageID selector in the GetMessage - relying 
on simply getting whatever message the server sends back next.

Also it removes the section 4.2. Effectively section 4.2 is an 
optimisation: for example to support unreliable-in/reliable-out a client

could do a createsequence+offer and never use the outgoing sequence. In 
this case there is an overhead, which 4.2 aimed to remove, but this 
simplifies the proposal by focussing on the bare minimum required to 
support the most common use cases, but still allowing the other use case

with a slight overhead.

I've also included a sample message flow which I hope helps understand 
the proposal and show the general usage.

Paul

-- 

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

http://feeds.feedburner.com/bloglines/pzf
paul@wso2.com

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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]