08 May 2002

Wed, 08 May 2002

there is no spoon responds with a question

there is no spoon writes:



backlinking back-atcha: David Watson has already responded to my question about how to use his getReferer web service. It sounds pretty simple and I can't wait to try it. Unfortunately, I've got a big project due Friday and I'm going to have to turn Radio off for a couple of days or I'll be in a world of pain. (Radio is like a siren in the Homeric sense (think of the creek/frog scene in "Oh Brother, Where Art Thou?")—it's always calling if it's on.) I'll play around with getReferer on Saturday (if all goes well between now and then). David has also explains why getReferer works the way it does. I think I understand the complexity issue, and I think David's solution is a great compromise to do everything he says—it provides an easy-to-use, low-overhead, nearly-universal solution (for Radio users). To automatically show referers by page, rather than by site, you'd need to write separate code for every server, right? And that doesn't seem practical. I agree. At the same time, all Radio-hosted sites run on the same server, right? So the specific, page-level log file parser for the Radio server would take care of a bunch of people, wouldn't it? Just a thought. Note to self: Get Webalizer. [there is no spoon]


No, all radio sites do not run on the same server. There is a server in radio, but that's generally not the one that's serving the web pages to browsers.

Posted at: 17:36 | permalink

David Weinberger talks linkbacks

Jimsblog has a link to a piece by David Weinberger on linkbacks. Link the linker. Heh.

Posted at: 17:13 | permalink

Jim comments on radio backlinking

Jimslog picks up the discussion on radio backlinking. I don't believe what Jim describes is possible in radio, unless perhaps you were serving your site off of the embedded apache inside radio, which I don't believe is a recommended configuration, at least not for sites with much traffic. Radio works with virtually any webserver, which is a virtue, but it's also a liability in this case because it's difficult to solve this problem without having a common scripting language executing in the webserver. There's also the problem of the fact that radio's usertalk scripting language is executed at publish-time not page-load-time in the browser. That basically forces you into a design that's custom-engineered for your webserver and platform as I described below in my response to Sam Ruby.

Posted at: 17:07 | permalink

Against Depression, A Sugar Pill is Hard to Beat

Washington Post has picked up on the story [( blogdex : recent )]

Posted at: 08:02 | permalink

RCS Proxy on xmethods.com

RCS Proxy is now listed on xmethods.com. This may be helpful for those who'd like to browse the interface using their WSDL analyzer or RPC Profiler.

Posted at: 07:57 | permalink

CocoBlog keeps on rollin'

Ugo Cei informs me that Ham Journalism is Tony Collen, whose Radio blog is here.

Posted at: 02:03 | permalink