Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Making Journals from Emacs 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Why not use the XML-RPC APIs that are out there so that you could leverage all the clients written for, say, the Blogger API and the metaWeblogAPI? (For those heathen who don't like to use Emacs.) Or you could just use a SOAP version of the XML-RPC API if you wanted.

    Seriously, though, this is a great addition.

    For future reference:

    Emacs package to update weblogs/journals [elisp.info] using XML-RPC APIs.

    SOAP.el [google.com] (to avoid forking off a call from emacs):

    The more mature xml-rpc.el [elisp.info].

    • Which APIs? I looked at the Blogger API and was unimpressed. There's no standard out there that I could find.
      • metaWeblog [xmlrpc.com] API allows you to do more than the Blogger API. Second, don't trust the offical docs on the Blogger API. Simon Kittle has a more complete set of docs [tswoam.co.uk]. I know, its annoying.

        Still, though the blogger API may not be impressive, it (along with the metaWeblog API) maps pretty closely to the API you've specified.

        • add_entry ~ blogger.newPost or metaWeblog.newPost (for titles/subjects)
        • modify_entry ~ blogger.editPost or metaWeblog.editPost
        • delete_entry ~ blogger.deletePost
        • get_entry ~ metaWeblog.g
        • But it doesn't support everything I need, it doesn't fully apply in what it does have, and this has been implemented for many months and a lot of people rely on it. So it isn't changing. :-)
          • I never suggested that you should change it. That would be silly, especially since you have other people using it. I appreciate the work done on this -- it gives me some great ideas.

            Still, as far as I can tell, there is only one missing call (get_uid_from_nickname) and there's no reason you couldn't bolt that on somewhere. (But your api is better with respect to authentication.)

            Would it be possible to get some introspection [sourceforge.net] or even an availableMethods call (like the MT API has)?
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.