You can read Mr. Cavnar-Johnson's comment here: http://weblogs.asp.net/craigmcmurtry/archive/2004/11/13/252837.aspx#256983.  I'm assuming that everyone else that read my original post did not misinterpret it, as he did, to mean that a service-oriented solution cannot usefully include message-queueing.  Of course, the point was that an architecture is not service-oriented unless it incorporates services, and a message-queue is not a service.  I'm sure most people don't think message queues are services, but I felt compelled to make the distinction because I kept hearing people say that systems in which XML messages get dropped onto queues are service-oriented purely because XML messages are getting dropped onto queues.