> ...the Java platform... requires a different API for each type of
> middleware/communication pattern.
I would like to see the JMS API get an update, e.g. to incorporate
features the vendors have been proving out on their own.
I think the Java community as a whole has been doing a good bit of API
development, e.g. Spring, Pico, etc. Indigo may inspire more coherency
across API's. There have been articles published on making JMS easier
to use by wrapping a Stream API around them, by mitigating JNDI setup
with Spring, etc.
> Microsoft's Windows Communication Foundation (aka "Indigo")?
Has Indigo proven itself yet? When will it ship? How does Indigo
compare to JMS for queues and pub/sub? Does it support those models
directly, or try to hide them? Which approach is better?
I think there is a lot to learn and once MSFT gets Indigo into
production we can find out more.
-Patrick
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.
