|
Thursday, February 14, 2002 |
|
When access is turned off for a particular host and you submit an XMLRPC request from that host against the Radio server, it responds with an XML body that contains error information, but the response itself is marked as 200/OK. Maybe this is the correct behavior in teh XML world?
In any case, it causes hell from AppleScript because it doesn't seem to be possible to grab the raw response body itself (that I can figure). AppleScript definitely generates an error, but it seems to be totally generic-- i.e. there is no way to recover the response body and see what is really going on (or provide feedback to the user). |
|
A couple of Radio related issues; It seems to be impossible to require Radio to use authentication when talking with the localhost. Why would you want to do this? Imagine you were working in a computer cluster on a network account. It is likely someone could ssh into the machine running Radio and, because they are on the localhost, do anything they want to your Radio desktop either from the command line or, if they are feeling particularly evil, by port forwarding 5335 to 5335 on their own machine and using a full blown browser.
Also, it isn't 100% clear if it is possible to require a username/password to access the XML-RPC/SOAP interfaces *at all*. I can restrict access via hostname/ip address, but that doesn't help if I want to be able to communicate with a remote Radio environment in a fashion that doesn't open it up to everyone the subnet (or, at least, anyone who happens to log into the machine I'm using). |
|
RadioService v0.9a2 is available for download.
There is still a bug where RadioServices will work correctly for the first post when the post request caused the app to launch. Every post after that works, though. Not sure what is up with that.
The next step is to get remote posting to work. |
|
Fixed a problem with the commit mentioned earlier. It is really committed now. 12:18:34 AM 
|
|
In the day after the release of RadioServices, I have been amazed at the response. It seems that most folks with a single desktop Radio based installation have had no problem. There hasn't been much feedback outside the Radio community, but there hasn't been any attempt to push it beyond Radio (since it was created to solve an immediate need I had with Radio). Some of the most frequently asked questions and answers (from someone whose knowledge of Radio is fairly shallow). Most all of the links assume Radio is running on the local desktop. How should Radio be configured to work with RadioServices (or apps such as BlogApp)? You need to make sure that the XML-RPC interface is enabled. Then, enable the the Blogger API. When RadioService asks for my password, which do I use? On this page, you will find a list of Radio password. Likely only one labeled default. Whatever that password is, that is the one you want to use. If you happen to have forgotten it (I did-- you create it when you first download Radio, 30 days before the $40 commitment decision), go to the Setup page and use the Forget your usernum and password? form to have your password sent to you. Does RadioService work with remote Radio applications? At the moment, likely only if you turn off all secuirty and enable full remote access. Obviously, a less than ideal situation. I have to figure out how to deal with the authentication issue from the XML-RPC engine in AppleScript (if possible). If not, I'll toss AppleScript and use Java instead. Will RadioService work with non-Radio based systems? Sure. Absolutely. Because I have never tried it, I can say with complete and utter confidence that it will work just fine because it is all about standards and nothing but standards.
It should work fine save for the whole HTTP authentication stuff. |
Last update: 1/23/03; 11:08:34 .
