This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Answer to an Indigo Question on OperationContract
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I just attended an excellent talk by Steve Swartz on an Indigo Overview. Even though I have been in the Indigo SDR > 1 year, I got a lot out of it. One thing I want to pass on is an answer to a question someone in Vermont asked me during my SOA/Indigo talk, which was why can't I put [OperationContract] on a section of operations rather than having to specifying each one, one by one? I answered that Indigo was forcing you to be explicit on your Service Contract, on what operations you want to expose. That is most of the answer. As Steve amplified, that with Microsoft being all about security before rather than after now-days (ala CLR methods private by default rather than public). So you don't want to expose an operation for instance that is meant to be a “helper method” that might expose 10,000 credit cards! Indigo is secure by default.
Previous Topic
