Comments on: WCF or ASP.NET MVC http://eikonne.wordpress.com/2008/06/05/wcf-or-aspnet-mvc/ All and sundry Mon, 17 Aug 2009 03:35:06 +0000 http://wordpress.com/ hourly 1 By: Eb http://eikonne.wordpress.com/2008/06/05/wcf-or-aspnet-mvc/#comment-51 Eb Mon, 28 Jul 2008 11:34:01 +0000 http://eikonne.wordpress.com/?p=41#comment-51 Zygimantas - I think you are possibly mixing up a couple of things and possibly calling them "channels" e.g. REST and WS are not channels. However, I do believe I understand your point which is the possible exposure of the same service over HTTP, TCP, MSMQ etc. If your architectural style is REST, then it potentially influences your technology choice and in my opinion ASP.NET MVC may be the better choice. If the architectural style is RPC, then WCF may be a better solution. Zygimantas -

I think you are possibly mixing up a couple of things and possibly calling them “channels” e.g. REST and WS are not channels. However, I do believe I understand your point which is the possible exposure of the same service over HTTP, TCP, MSMQ etc.

If your architectural style is REST, then it potentially influences your technology choice and in my opinion ASP.NET MVC may be the better choice. If the architectural style is RPC, then WCF may be a better solution.

]]> By: Zygimantas http://eikonne.wordpress.com/2008/06/05/wcf-or-aspnet-mvc/#comment-50 Zygimantas Tue, 22 Jul 2008 10:28:05 +0000 http://eikonne.wordpress.com/?p=41#comment-50 WCF has the advantage that you can output the same service to multiple channels (JSON, REST, WS, TCP) with no code changes. WCF has the advantage that you can output the same service to multiple channels (JSON, REST, WS, TCP) with no code changes.

]]>