Re: [service-orientated-architecture] Integration via jms, web services, or rmi?

[Steve Jones]

OOoh quite a bit, I'm writing something at the moment actually using the wonderful concurrent package that.

My point is that something like BPEL which has built into its "language" the concept of a request response and can handle behind the scenes the "block", "poll" or "event" question is simpler for most people than trying to understand how threads really work.

Async is hard, and like threading there are less than 5% of people who can actually do it well (and I'm being generous with 5%), so if you are doing async stuff its a good idea to pick an environment that makes it simpler to do async by hiding lots of the challenging bits from you.

If I had 20 Doug Leas on my teams I'd always use Java for async, unfortunately I don't.

On 27/09/06, Gregg Wonderly < [EMAIL PROTECTED]> wrote:

Steve Jones wrote:
> If you are doing Async, have a big think about using BPEL as a
> co-ordinator as Java is pretty poor at Async.

I'd like to know how much experience you have using Java to do async, and what
you used for your async implementation. Java has no influence at all on how
well async happens. It's all about software design and architecture. If you
use the wrong implementation, you will in fact have poor async experiences...

Gregg Wonderly

__._,_.___

SPONSORED LINKS

Computer software program	Computer software spy	Computer job
Database software	Discount computer software

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___