August 2006 Archives

One of the problems with WWW based Web services is that they're not always very reliable. It's all very well talking about the multitude of Web services that are going to be on the Web but when you actually go looking using a tool like Google you find that there isn't as many as you'd think, they're is little indication that they are current, and there is no guarantee they will be there tomorrow.

I went looking for the simple stock quote Web service and found only a handful. I found one that worked well on the xmethods.net Web site. I found the example in the Ruby Cookbook (page 630). I'm not sure if it was due to my posting my Ruby based Web service client on Tuesday, and it causing some sort of spike in usage, but since yesterday this service no longer exists! It's not even listed anymore. So those of you that were thinking "this Ruby program doesn't work!" are right! It no longer works. I will be fixing that.

When you do find a Web service using the Google approach to finding them, they might be dated 2003, or something like that. Which is fine - if a service written in 2003 worked and still works fine then there is no need to change it. However as a user you'd still like to know that it is current and won't be gone in like ... a DAY!

So then I found a WSDL for a simple Stock quote Web service on the IBM site. I had to change my Ruby code to use the WSDL instead of the API that uses the URL and namespace. But as it turns out this service no longer exists either!

So I'll hunt down another stock quote Web service with a similar schema and post the updated Ruby file to the end of this post later. There are several out there, it's just a matter of finding whcih one is still there. I might use Yahoo.

I started working on a project over the weekend to pull together a demonstration of using Ruby, and RSS or Atom and Web services. I also want to add Artix and it's Data Services into the mix later. The final result will be a mashup but I want to start publishing some of the work as I go along.

I hadn't worked with Ruby before. I had alrady started learning PHP but was encouraged by Steve Vinoski to start looking at Ruby. Jim Watson and Greg Lomow, whom I had worked with developing a language back in 1997, finally convinced me. So I bought two books: Ruby Cookbook and Programming Ruby The Pragmatic Programmers' guide. I then loaded up a bunch of bookmarks in my browser of Ruby sites and off I went.

Then it was off to work on some code.

First I built a couple of classes to write an atom based feed - an atom.xml file. These two classes handle writing out the feed header information and then each of the entries.


I see that Barry has been busy over at Haute Techno with a new Mashup using CeltiXfire (aka Celtix) and a number of other technologies including Google Maps. (Google Maps must be the most widely used set of web service APIs for mashups.)

You can download the demo from the site which includes documentation. Barry says that it was the most fun he's had in a long time and that he'll be evolving the mashup.

I'm looking forward to seeing more CeltiXfire and Artix based mashups soon. I believe Steve Vinoski has been working on some too.

IP's world domination is growing at a great pace. I just talked to my friend Tom Van Horn on Skype while he was travelling back from India via Europe on a Lufthansa flight. I'm sure this type of thing has been done already but it was a first for me.

Tom had emailed me from the plane and explained in the email that he was using the Connexion service from Boeing. I emailed him back-and-forth a couple of times (at one point mentioning that IONA's Orbix was an enabler of the Connexion solution), and then decided I'd IM (instant message) him using Skype.

After some more back-and-forth instant messages I decided it would be cooler to just ring him using Skype. But I was afraid Tom might not have headphones or other equipment on the plane. I asked him over IM and he replied that he did not have a microphopne but he did have headphones. We decided that I would just talk and that Tom could IM back; telling me if the sound quality was good or bad. So I called him and when the ringing stopped I just started to talk. Tom replied over IM, "It's great quality". Of course it wasn't really a two-way conversation and maybe the quality wouldn't be so good if it were two-way. We'll test that the next time.

After we hung up my friend Dave Keller called me on Skype. I told him about Tom's and my experiment. He was impressed too and asked "I wonder how much that costs?" I said I didn't know but I'd ask Tom the next time .... "wait a minute. I'll just ask Tom now." I sent an instant message to Tom and he replied with the cost. "Talk about real-time", Dave said to me.

Pretty neat! What's cool too is that I'm going to IM Tom the link to this article so he can read this story before he lands!

(BTW according to Tom the cost is $26.95 for 24 hours that can be used across multiple flights. Or $9.99 per hour. )

Older article on Skype here.

Who is IPBabble

William Henry IP Babble is the personal blog of William Henry.

I have approx. 20 years experience in software development and distributed computing and hold a M.Sc from Dublin City University. I'm currently working in the office of CTO at Red Hat on the MRG product. This weblog is mine personally and is in no way funded by Red Hat. I will try to post independent views but understand that most likely I have a bias based on the influence of working with standards based middleware for over a decade. (See disclaimer below)

October 2008

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Disclaimer

The views expressed in this blog are solely the personal views of the author and DO NOT represent the views of his employer or any third party.

About this Archive

This page is an archive of entries from August 2006 listed from newest to oldest.

July 2006 is the previous archive.

September 2006 is the next archive.

Find recent content on the main index or look in the archives to find all content.