> >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 haven't used JMS in over 4 years but Indigo fully supports durable
messaging with both queues and pub/sub. I wouldn't say hidden but it
makes a lot of it easier with abstracting them into the right bindings.
Will Indigo allow for plugging in providers in the same way as JMS does?
For example, would it be possible to use WMQ or ActiveMQ (using the
OpenWire.Net provider) behind the Indigo API?
I find that one thing sorely missing from .NET today is an abstracted
API for messaging systems. Hopefully, WCF can fill this gap.
/niklas
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.
