Radio web services

s l a m is not supposed to be dedicated to the subject of blogging or even tinkering with Radio UserLand. Still, I suppose I'm just like most geeks discovering a new technology or tool, I jump into it and put the rest on the backburner, at least for a short while. Before I turn s l a m back to its original intent, here is a quick rundown of what I learned on the subject of web services with Radio. When it is running, Radio acts as an XML-RPC or SOAP server. A web service for Radio is written in UserTalk, Frontier/Radio's scripting language. The script's source text file, when dropped in the Web Services subfolder of Radio's application folder, is automatically compiled and stored into the Radio.root object database, in the user.betty.rpcHandlers.radio (XML-RPC) and user.soap.rpcHandlers.radio (SOAP) tables. The agent responsible for the scanning and compilling is builtins.radio.thread.agents.watchMacros(). It is scheduled every 10 seconds or so. As of the current version, it can be spooked by the .DS_Store invisible file that may appear in the Web Services folder in MacOS X. Deleting .DS_Store keeps it happy. Invalid UserTalk scripts fail compiling and are not integrated. When making modifications to a script that is already compiled in Radio.root, it is better to manually delete the existing version in user.betty.rpcHandlers.radio and user.soap.rpcHandlers.radio. If valid, the updated version is compiled within the next 10 seconds. To call the web service from a Radio macro, use something like <%params = {parameters_list}; xml.rpc ("127.0.0.1", 5335, "radio.script_name", @params)%> or <%params = {parameters_list}; soap ("127.0.0.1", 5335, "radio.script_name", @params)%>. It is of course possible to make calls from other systems, provided the system running Radio is accessible by TCP/IP. My main sources of information were Dave's tutorial, Jon's subscriptions displayservice and the Radio-dev discussion group.

Jon's widget now operational

It took a lot of assistance from knowledgeable people in TangledThread and Radio-dev to help me figure out that there is a problem with the way Radio currently updates its web services scripts from the Web Services folder in MacOS X. I've reported the problem and its work around here. Meanwhile, my current subscriptions are now correctly displayed in s l a m on the right pane. To celebrate, I've created a TinyXml gif and modified Jon's script accordingly. Thanks to Jon, Ralph, Andy and Jake for their patience :-)

Marc Barrot: web services

Radio web services

Jon's widget now operational