... or clarify. Thanks. Dave, Answer: A question and a comment. Clarification: It seems to me that the existing MW API is focused (whether by design or happy...
My first thought was that it would be more flexible and more consistent with the spec if, instead of just images, it worked with any type of media object. ...
Thanks for the explanation. In the future it would be good to provide the background with the question. Actually the connection to RSS 2.0 wasn't initially...
<delurk> ... I realize that this was a pre-RFC, but I think Roger brings up a good point. It sounds to me like as a matter of policy, new methods should ...
Good point. I did it that way because I make lots of GIFs and JPEGs myself and I have code that can determine the height and width of those. But no reason to...
Subject: New Message: Re: A new API for sequences of photos? ... http://members.jcom.home.ne.jp/mtpsoft/limon/ [1] ... simplicity. That simplicity was part of...
Subject: New Message: metaWeblog.newImageSequence, OPML, etc. ... performing basic posts to a weblog. After a set of photos is uploaded, a "Post to blog"...
Greetings! I've been working on the long-delayed unified spec for the MetaWeblog API. It's been documented in layers across several pages on the XML- RPC site....
One thing I didn't pick up from reading the spec is, is there a standard practice for selecting a postid to put in the getPost() call? In other words, how...
... standard practice for selecting a postid to put in the getPost() call? In other words, how would I tell my desktop authoring tool that I want to edit "this...
Thanks for the reminder Brent (I forgot to check on the previous spec), I just saw that Dave updated the current spec with it as well. Since we're on the...
Actually this one is not in the metaWeblog spec, it is in an RFC that you posted in December last year. http://www.xmlrpc.com/discuss/msgReader$2366 I'm going...
Description is just the description, nothing more. The name of the category is the name of the sub-struct for the category (recall that XML-RPC structs have...
... +1, though I'd make catId mandatory (and suggest duplicating description, if the blog system in question doesn't have ids separate from names). OTOH, since...
... category is the name of the sub-struct for the category (recall that XML-RPC structs have names). The name of the struct must be unique, making it a...
I would argue that getRecentPosts actually is a standard part of the metaWeblog API. It's supported by Manila, Radio, Movable Type, and probably others. (In...
... FWIW, metaWeblog.getRecentPosts is already in use out in the wild (and not just as part of the MovableType API), and has pretty much become a de facto part...
When adding this to the new spec I would definitely specify really well what "recent" meant--adding a parameter for the cut-off date (optionally empty for all...
I added a new note [1] in the comments section of the MetaWeblog API spec explaining that errors are handled through the fault-reporting procedure described...
The revisted MetaWeblog API spec is available, with caveats removed, here: http://www.xmlrpc.com/metaWeblogApi It's now safe to develop applications based on...
... Thanks! This is an important entry point, since it provides a client app a way to get the post ids, which are essential for the basic entry points. The...
Noticed that the current MetaWeblogAPI spec is missing a deletePost. I thought this was added about a year ago. Seems to be gone now. Just wondering. Randy...
