I wasn't suggesting WS-RX *over* AMQP. I was suggesting a mixture of the two - an Open JMS implementation with a well-defined wire protocol and then bridging into Web Services. I personally think if we can make WSRM/RX fast enough then we can get very wide adoption.
As regards "queued" WSRX, we already offer that. WSO2 Tungsten implements it as does code from IBM and others. RM is "just" a wire protocol and doesn't talk about implementations, but certainly the Apache implementation was designed to support persistent reliability.
Paul
On 6/23/06, Guy Crets <[EMAIL PROTECTED]> wrote:
Paul,WS-RX over AMQP: fine within organizations, but getting through corporate firewalls really requires HTTP(S). On the WS-RX part: please give us "queued" WS-RX, whereby messages are persisted. With queued WS-RX, we have a nice alternative for AS2, ebMS, RNIF and so on.Regards, Guy Crets-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Paul Fremantle
Sent: vrijdag 23 juni 2006 17:25
To: [email protected]
Subject: Re: [service-orientated-architecture] AMQPAnne
I see a lot of opportunities for WS-RX AND AMQP. For example, bridging between systems which use the MOM model and systems that use the Service model. I also see opportunity for WSRM/RX (and as the chair of the TC you can expect some bias!) as a truly interoperable model that IBM and Tibco are both implementing.
There is also an effort in Apache to produce a pure C version of the WSRM/RX protocol that I hope will perform competitively with MQ and other persistent reliable messaging engines.
Paul
On 6/23/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:I think this sentence is a bit optimistic:
JMS APIs over AMQ could easily interoperate with .NET clients or any other language or platform that can communicate via AMQP.
This would only work if the JMS vendors and Microsoft abandon their investments in proprietary protocols and adopt AMQP. Such a move might breathe new life into the MOM market, but can you see 90+% of the Fortune 500 converting their existing apps from MQSeries and Tibco RV to AMQP? These protocols are as entrenched as CICS/COBOL.
Where I see a great opportunity is WS-RX over AMQP.
Anne
On 6/23/06, Stefan Tilkov < [EMAIL PROTECTED] > wrote:On Jun 23, 2006, at 7:22 AM, patrickdlogan wrote:
> "standardize best practice - yes, if you can, absolutely, like what
> we're looking into currently with AMQP, but this is not always
> possible"
>
> Please say more.
>You mean about AMQP or about the process?
If it's the first, here's some more info: http://www.infoq.com/news/amq
Stefan
> -Patrick
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
__._,_.___
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
