Take the 2-minute tour ×  We have an R Server (R is a
programming language used in statistical analysis) that
basically takes a script and a csv file, processes some data and
returns results as text.  I need to write a service on the R
server so that .net clients (could be .Net Windows Forms, or
ASP.Net) can connect to the R server, submit the script and CSV
file, and get the results back.  I'm confused by the many
different bindings available to me and information on the web
seems to be sparse/scattered about what one to choose.  Also, is
it best to run the service in IIS, or as a separate "command
line" type listener service (the latter seems ugly compared to
IIS and I have no idea why anyone would choose to do this if
they could run it in IIS)?  share|improve this question  4
Answers 4  up vote 9 down vote accepted  Personally, I'd
recommend the simplest binding that gives what you need. I've
done quite a lot of WCF (some quite complex), and I've never had
to use anything other than BasicHttpBinding; this