Legacy Support?
On Wed, Dec 18, 2013 at 10:20 AM, Katherine Moss <katherine.m...@gordon.edu>wrote: > Then where do ASMX and SVC services fit in these days? > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Michael Ridland > *Sent:* Tuesday, December 17, 2013 5:55 PM > *To:* ozDotNet > *Subject:* Re: ASMX vs SVC basicHtpBinding > > > > > > WebAPI with JSON? > > http://www.asp.net/web-api > > > > Or if you want to have some fun you could use Node.js? > > > > Or there's NancyFX? > > > > > > > > > > On Wed, Dec 18, 2013 at 9:43 AM, Greg Keogh <g...@mira.net> wrote: > > Folks, I recently had a write a few web services and I had the choice of > using SVC with basicHttpBinding or the traditional ASMX Web Service. The > services only need to behave like simple libraries, passing strings and > simple class types back and forth. I've said before I think WCF is > an overweight "beast" which is great if you need to change bindings or > delicately configure its many settings (and you can figure out how to do > it!), but I don't need any of that stuff so I decided to use ASMX because > it's so much easier to code. > > > > Does anyone know if my decision makes things easier or worse for non-.NET > consumers? It looks like native apps on Android or iPhone might have to > consume my services and I was wondering if my ASMX web services might > irritate them. What is the preferred way of publishing a web service these > days that makes things easy and "open" for various consumers? Maybe REST is > preferred?! > > > > Greg K > > >
