>The API is not growing, the reference here is.
Ok, that's what I thought but you threw me with the living, growing stuff.

>>I figured like what was in here was better than nothing and would be nice to browse thru in the same fashion the app form the link I gave for VBers is.

>What's the difference?
One is online here, the other is available anytime. You could save the web page or copy and paste in a text file for offline viewing. Is that what you mean?

>>Oh, are you saying you'll create an XML source for me? (Note to self: not funny, time for sleep)

>Out of my hands. That would be up to Michel.
Again, I was confused thinking each Call was/could be changed but even with the reference growing - adding new Calls or more comments to an existing one, I was wondering if XML was a preferred method of providing data for a living, growing and ongoing data source


>> But seriously is this where Publish/Subscribe will be handy dandy too?

>Publish /subscribe wouldn't really come into the picture here, even if the app were distributed.

Won't P/S payoff in more ways than downloading data to web sites as per the example at NOLA DevCon? Can't it serve for updating data sources for other things? I guess I got to that with the following question

>>Not just web sites like MyFloristDeliver.com retrieveing delivery info from another florist but even to the desktop with XML over your internet connection?

>You could do that, and I have apps that do that now, but I don't see the use here. You write a client side app when a browser doesn't give you the functionality you need. Again, what's the problem with the browser interface?

I prefer a desktop GUI over a browser one myself whether online or off. Do you perfer browser interfaces?