The article Roots of the REST/SOAP Debate (along with many others like it) claims that SOAP web services have a limitation in that resources they work with are not directly addressable via a URI, but that you have to connect to the SOAP endpoint and then call a method on it. The analogy used is as follows...
There seem to be a lot of blog entries at the moment arguing over the relative merits of XML, JSON, YAML, S-Expressions, etc. as a data interchange format, and Web Services, WS-* Services and REST-style as the application protocol implementation. But while various articles make interesting academic points...
Most people find negative statements more difficult to comprehend than positive statements. You probably had to double-check the title of this entry to see if it made sense - I know I did! This isn't surprising if you think about it because a positive statements presents a concept which can be used...
One thing that irritates me about software development is peoples apparent obsession with sub-namespaces called "Common" which they use to contain code that is used throughout the rest of the project/solution. Common namespaces are a code smell which often means you don't really understand...
We've all been on them before. A salesman gets a request from a client to implement a "simple process", and the client books ten days work at a fixed cost which means you're obliged to deliver in that time. You go in, do the work to the minimum standard as that's all the ten days...
At my house I have a bit of a north pole theme with my hardware naming conventions. The laptop I'm writing this on is called ICECAP, my media center is called GLACIER, and my desktop is called ICEBERG. Even my wireless network is called AURORA BOREALIS. Now this is a bit of fun in a home environment...
On the MSDN forums there are usually a few posts each week along the lines of “Please tell me what you think of this…” followed by a fairly long listing of entirely uncommented code. Presumably the poster is looking for feedback on the quality of the code but they are missing the fundamental point of...