This approach is not only untested but will also require some additional processing on your part to finish populating the Radio CMS. That's the bad news. The good news is that your entire Blogger blog should now be a table in the object database and Radio/Frontier is rigged to the eyeballs for doing ODB stuff.No, it wouldn't. This is only a MT hack and it was a fluke involving auto-vivification of hash keys in Perl. The code was written to follow the spec.
The only way to get an entire Blogger blog using the API is fraught with danger; basically you have to get 20 recent posts (that's the upper limit), store them somewhere safe, delete them all from Blogger and start over again.
The process for importing into MT involves formatting the blog in a manner that lends itself to scraping and then you set your posts per page to something outrageous like 1000+
That said, the easiest way to import a Blogger blog into RU would be to format the templates as XML, set the page limit to <insert outrageous number> and rebuild your static files. Then you could slurp the file and parse it in Radio, saving everything to a table, like this :
local (server="yerhost.com") local (path="/path/to/bigfile.xml") xmlText = tcp.httpClient(server:server,path:path) xmlBody = string.httpResultSplit(xmlText) xml.compile(xmlBody,@workspace.bloggerData)
ls -laR command to an FTP client and and pipe it through to a series of SAX handlers/filters that ended with a single representation of all the changes. I suppose you could run a daemon on the server-side, every (n) minutes and output a dotfile for the client to read. Or maybe run a stand-alone XML-RPC server, at the remote location, that returns a data structure of the directory layout. If you assume that the server has more processing power/tools than the client, there could be a second method that accepted an XML representation of the client-side directory structure that returns a list of changes. But the point is ...the point is that some pointy-head somewhere is going to seize on this as an opportuntity to write YA markup language... that this is really just a daemon with a dumb GUI for storing paths and an authentication. I wonder how hard it would be to hack the Amphetadesk framework to do this since it's essentially the same concept : every once in a while, do something over here with this login. see also : XML::Directory and I'd love to retire XML::Handler::2Simple in favor of the forthcoming XML::Simple
"Life's A Bitch And Then Ya Die" Usually in response to whining complaints.
ex. A. "Can you believe it? He only gave me a 3% raise!" B. "Yeah, yeah, labatyd."
Fugacious \Fu*ga"cious\, a. [L. fugax, fugacis, from fugere: cf. F. fugace. See {Fugitive}.] 1. Flying, or disposed to fly; fleeing away; lasting but a short time; volatile. Much of its possessions is so hid, so fugacious, and of so uncertain purchase. --Jer. Taylor. 2. (Biol.) Fleeting; lasting but a short time; -- applied particularly to organs or parts which are short-lived as compared with the life of the individual. web1913
fugacious adj : enduring a very short time; "the ephemeral joys of childhood"; "a passing fancy"; "youth's transient beauty"; "love is transitory but at is eternal"; "fugacious blossoms" [syn: {ephemeral}, {passing}, {short-lived}, {transient}, {transitory}] wn