| « Remoting et RCW | A .NET book that really rocks » |
Is .NET Remoting a bad choice ?
I would like to have your opinions about the future of the .NET Remoting technology. Is .NET Remoting a bad or a good choice for our new projects to come ? Do we have to make the difference between custom frameworks (that must consider future evolutions) and simple (even big) applications that can safely rely on .NET Remoting for their architecture, even when Indigo finally ships ? My opinion is clear : since .NET Remoting won't disappear with Indigo, it doesn't matter yet, except for application frameworks maybe. We can safely continue to use .NET Remoting as if we had never heard about Indigo.
And one more question : how can we design a new application so that we use .NET Remoting but can easily shift to Indigo later on, with the less possible efforts ?
4 commentaires
Since Microsoft announced the development will be stop and the arrival of a competitor technology, that means Remoting is dead.
Maybe not immediatly, but dead. That's clear and I can't imagine a "Cobol-like destinity" to this bad-formed technology.
The choice now is that one: if your application is already Remoting colored or about to be delivered, change anything.
If your application is not to be deployed before 1 year, consider indigo as a solution.
But I agree with Laurent that the .NET community should consider design patterns that isolate as much as possible the remoting part. I don't know if it's easy. But even a partial solution is by itself a good one.
Does anybody know the true impact of remoting on real .NET projects?
Amethyste
My take is to go on with remoting (no real choice here), isolating communication code as much as possible (as usual) to be able to locate easily what will be inpacted when time to move onto something else comes.
http://www.theserverside.net/news/thread.tss?thread_id=27235
Flux de commentaires pour cet article