PyDS XMLRPC weblog API

Ok.

To get my feet wet, I thought I would start on something simpler, and try interacting with PyDS via the weblog API's over XMLRPC.

I am having mixed success so far, am hoping someone can clue me in on where I am going wrong. By 'mixed success', I mean that some calls work fine, others do not.

After opening a line to the server's xmlrpc channel like this:
   blog=xmlrpclib.Server('http://localhost:4334/RPC2/weblog')

I am then able to make successful calls to getRecentPosts and to getCategories.

But I cannot get newPost or getPost to work for me.

newPost tells me:
   Fault: <Fault 1: 'Method not found in namespace weblog:newPost'>

getPost gives me:
   Fault: <Fault 1: 'Authentication failure:P8'>

P8 is the postID as listed by getRecentPosts. I am sure that my authentication info is fine. All I could guess for this is that I am not providing the proper parm list to getPost. I browsed the MetaWeblogAPI.py and Blogger.py files for clues; am I looking in the wrong place.

BTW, I have worked with XMLRPC before, but this is my first work with the weblog api's. If these are really either XMLRPC issues or weblog API issues, and not PyDS issues, pardon me, just let me know.

Any help appreciated,
Thanks,
Rand
> -------- Original Message --------
> Subject: Re: [Pyds-dev] Hierarchical Categories
> From: "Georg Bauer" <gb-BRhJDZTO+/[email protected]>
> Date: Sat, January 31, 2004 10:49 am
> To: rand-kzPqTZqrtG+O+QkcXTtFxKWz8mPg4b/[email protected]
> Cc: pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
> 
> Hi!
> 
> > I have begun using categories, which are great, but as I increase the
> 
> > number of categories I want to use, this will become unwieldy. What 
> 
> I've thought about this, it wouldn't be too complicated. The first
> part
> would be to design a useable web interface to edit structured data -
> that's the biggest problem, as editing hierarchical stuff with web
> browsers isn't too nice (no, Javascript and DOM hacks don't cut the
> cake
> here - I prefer it that PyDS will allways be useable with w3m or even
> lynx). Next would be a category selection for the new posting form -
> you
> need to select what categories your post is in. The same problem with
> hierarchical data in Webforms, only this time a bit complicated by the
> fact that the new posting form needs to be terse enough to fit on a
> screen. If that's done, you only would need to go through the source
> and
> change all category comparisons to make use of a central
> "postingInCategoryOrSubCategory" function that makes use of the
> defined
> category hierarchy. This last work actually is just that - work.  Not
> very complicated. That's not the case with the visual representations,
> though ;-)
> 
> > I feel like the basic infrastructure might already be there, since
> dates 
> > sort of work this way now, with a hierarchy that looks like yyyy / mm
> 
> 
> Actually the hierarchical view to dates is somewhat burned into the
> inner system and quite different from the category handling.
> 
> > Are there any plans to do anything like this?
> 
> No current plans, sorry. But people are allways free to supply patches
> :-)
> 
> bye, Georg