On Tue, Dec 6, 2011 at 4:44 AM, David Kean <[email protected]> wrote: > Using SOAP (default protocol for Web Services) can be hard to consume by > other languages when its produced by .NET (and in general its hard unless you > have tools to help you generate code). > > REST seems to be the way to go these days, WCF supports it: > http://msdn.microsoft.com/en-us/netframework/dd547388 >
SOAP is the way to go if you want non-trivial security I thought > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Rob Andrew > Sent: Monday, December 05, 2011 4:31 AM > To: 'ozDotNet' > Subject: Business Logic Service > > Hi All, > > I have been asked to write a business logic layer that is to sit upon the > 'net. This layer is to act as a 'service' and provide it's features to a > number of consuming clients (Ipad, windows, web, etc). Idea is to code this > in C# and back it into SQL Server or similar. > > I was considering web services, but was wondering whether there are other > options available these days that might be more in tune with varying clients? > > Any thoughts? > > Thanks, > Rob > >
