cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@codeconsult.dsvr.co.uk>
Subject RE: [RT] Cocoon as OS
Date Sun, 03 Feb 2002 19:05:21 GMT
On 02.02.2002 17:14:56, Brian Topping <topping@digidemic.com> wrote:

>. . .
>Methinks JMS is too slow for this as a generalized transport.  
>. . .

It all depends on how fast/slow the back-end processes are. If we're speaking of a database
query + XSLT pipelines on the back-end, the JMS exchange can be just a small part of total
request processing time.

I wouldn't use JMS as a "generalized" transport though, but having an option to plug it in
for the most complex/big/slow systems is certainly an plus.

>. . .
> It *does* seem applicable in a
>workflow management scenario though, putting a document "on the bus" for
>different sinks to process would work well, because the performance
>expectation on CMS use cases aren't usually near that of OLTP/web
>browsing.
>. . .

Agreed, having multiple JMS queues/buses in a CMS setting is certainly a good solution.

- Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message