>Has Indigo proven itself yet?
Indigo has proven itself for our company. We have been using Indigo in production since last September. We actually have some banks using our stuff right now and our whole SOA based product is centered around Indigo Services. We have found extremely easy to understand and use - most of our stuff has been able to completly change its behavior from a WS-* compliant behavior to cross-process NET TCP with just one line of change in a config file if we needed to do it.
>When will it ship?
I know the date but I am not allowed by my agreement to state it. I can say generally in the timeframe of Vista.
>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. Here is a pub-sub example:
// The Service implementation implements your service contract.
[ServiceBehavior(InstanceContextMode=InstanceContextMode.PerSession)]
public class SampleService : ISampleContract
{
public static event PriceChangeEventHandler PriceChangeEvent;
public delegate void PriceChangeEventHandler(object sender, PriceChangeEventArgs e);
ISampleClientContract callback = null;
PriceChangeEventHandler priceChangeHandler = null;
//Clients call this service operation to subscribe.
//A price change event handler is registered for this client instance.
public void Subscribe()
{
callback = OperationContext.Current.GetCallbackChannel<ISampleClientContract>();
priceChangeHandler = new PriceChangeEventHandler(PriceChangeHandler);
PriceChangeEvent += priceChangeHandler;
}
//Clients call this service operation to unsubscribe.
//The previous price change event handler is deregistered.
public void Unsubscribe()
{
PriceChangeEvent -= priceChangeHandler;
}
//Information source clients call this service operation to report a price change.
//A price change event is raised. The price change event handlers for each subscriber will execute.
public void PublishPriceChange(string item, double price, double change)
{
PriceChangeEventArgs e = new PriceChangeEventArgs();
e.Item = item;
e.Price = price;
e.Change = change;
PriceChangeEvent(this, e);
}
//This event handler runs when a PriceChange event is raised.
//The client's PriceChange service operation is invoked to provide notification about the price change.
public void PriceChangeHandler(object sender, PriceChangeEventArgs e)
{
callback.PriceChange(e.Item, e.Price, e.Change);
}
}
On 5/1/06, patrickdlogan <[EMAIL PROTECTED]> wrote:
> ...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
--
Sam Gentile
INETA Speaker, Microsoft MVP-Solutions Architect, UG Leader Beantown .NET
.NET Blog: http://codebetter.com/blogs/sam.gentile/default.aspx
.NET Portal: http://samgentile.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.
