blog-service
About
Blog-service will provide a DBus API for easy blogging from different programs.
Goals
- Wide support for blog APIs:
- MetaWeblog
- Blogger 1.0
- Atom
- LiveJournal
- Easy to use and versatile API
- Connection independent
- Posts will be sent when there is a connection
- Minimize memory usage
- Only load posts etc when needed and free after not being used for a while (connection tracking?)
- Stop service if network monitoring allows us to
API draft
ARRAY(STRING:api) org.MaemoHackers.BlogService.get_supported_apis() org.MaemoHackers.BlogService.add_blog(STRING:api, ARRAY(DICT(STRING:field, VARIATOR:field_value))) ARRAY(DICT(STRING:field,VARIATOR:field_value)) org.MaemoHackers.BlogService.get_blogs(ARRAY(STRING:field)) ARRAY(DICT(STRING:field,VARIATOR:field_value)) org.MaemoHackers.BlogService.blog.get_posts(ARRAY(STRING:field)) ARRAY(STRING:category) org.MaemoHackers.BlogService.blog.get_categories() BOOLEAN:status org.MaemoHackers.BlogService.blog.create_category(STRING:category) BOOLEAN:status org.MaemoHackers.BlogService.blog.create_post(ARRAY(DICT(STRING:field,VARIATOR:field_value)) BOOLEAN:status org.MaemoHackers.BlogService.blog.edit_post(STRING:post_id, ARRAY(DICT(STRING:field,VARIATOR:field_value))
The field names will follow Atom names, like "title", "category", "description" etc. blog-service will not do anything special to these, and custom headers that BlogService doesn't know about can be defined, and they will be sent if the blog API is extensible.
TODO
- Implementation.
Wishlist
Blog
- blog-service revisited
Fooling around with dbus-glib, I decided to redesign the BlogService DBus API. The idea is the following; different blogs are available at different object paths, the default blog will be available as /org/MaemoHackers/BlogService/default or similar. The API is somewhat described in maemo-hackers wiki; the .xml files in svn repository have not yet been updated. [...]
- Lunch meeting over maemo-blog
- Yarr, cursed be the wordpress.com xmlrpc API
