In the past I've done blog posts on RESTful web services, showing how to do it in everything from Ruby to ASP.NET to WCF and even the ASP.NET MVC Framework. In this blog post, it's Java's turn.

In this blog post in the series I am going to cover some points about wire formats and which formats I like and which formats I dislike, and why.

In this first post of many, I will be giving my personal opinion on the state of Web Services programming today. This post covers my thoughts on REST.

I recently posted a blog about consuming a POX service with Cocoa. At the same time I managed to upset someone that I admire. This is what happens when bloggers don't have copy editors!

In a previous blog entry, I talked about how to consume a POX service using Cocoa. In this entry, I talk about how to create that POX service using ASP.NET MVC and how incredibly easy it is. Makes you wonder why anybody uses SOAP anymore...

In this blog post I'll take a look at the Objective-C/Cocoa code required to consume a POX service hosted by an ASP.NET MVC application.

Assuming you get the Wayne's World reference, read on: In this day and age of Web 2.0 and exposing software as a service, has the number of new and modern possibilities dulled our ability to create good clean C/S apps?

While it is fantastic that you can bind ASP.NET controls to LINQ to SQL data, a lot of the time you might want to be exposing that data via web services, or better yet, raw XML web services (POX) with no SOAP. In this post I cover this task.

This blog entry summarizes my experience creating a Silverlight application that consumes data from a POX service written using Orcas Beta 1

I've recently run across a spot in the WCF POX messaging scenario that should be raising an exception and isn't