{"id":495,"date":"2008-07-15T06:35:23","date_gmt":"2008-07-15T13:35:23","guid":{"rendered":"http:\/\/www.alephnaught.com\/Blog\/?p=495"},"modified":"2008-07-15T06:35:23","modified_gmt":"2008-07-15T13:35:23","slug":"taking-a-look-at-atomserver","status":"publish","type":"post","link":"https:\/\/www.alephnaught.com\/Blog\/2008\/07\/15\/taking-a-look-at-atomserver\/","title":{"rendered":"Taking a look at atomserver"},"content":{"rendered":"
\n

I read the XML Daily Newslink, and saw the following reference:<\/p>\n

AtomServer Helps Serve Up AtomPub
\nTaylor Cowan, O’Reilly Technical<\/p>\n

The most interesting development within the XML world of late is AtomPub.
\nIt abstracts the details (however simple they may be) of REST and
\nprovides them in a well specified protocol. Instead of writing home
\ngrown RESTfull web services, merely decompose your domain into
\ncollections or listings of XML blocks and let AtomPub handle the details
\nof query, create, delete, and update. One attractive benefit is that you
\ncan bank on a plethora of AtomPub client implementations…today.
\nFurthermore, many services (gdata – Google Data APIs) are sprouting up
\nso that the domain is familiar. Connecting to an RSS feed has always
\nbeen simple, now we can detach ourselves from the dark days of SOAP
\nover-engineering and provide data to the clients who want it with ease.
\nSo clearly I like Atom…but something has been missing. Until recently
\nyou’d be on your own in deciding how to implement the protocol. Many
\nthings are left to the particular implementation such as the URL format.
\nThe first thing to come along for Java developers was Abdera. This
\nmakes it possible to quickly write your own AtomPub server, however,
\nit does require one to write more than a few lines of code. Having
\nplayed around with Rails I could imagine that it wouldn’t be too far
\noff until we had something that made creating and binding an Atom server
\nto a database simpler, and it’s finally here in AtomServer. In their
\nown words, “AtomServer is a generic data store implemented as a
\nREST-ful web service.” More specifically, it’s a generic data store
\nimplemented as AtomPub. I downloaded the distribution and I was able
\nto get it running easily.<\/p>\n

http:\/\/news.oreilly.com\/2008\/07\/atomserver-helps-serve-up-atom.html<\/a>
\nSee also Atom references: http:\/\/xml.coverpages.org\/atom.html<\/a><\/p><\/blockquote>\n

For those of you that don’t know, Atom<\/a> is a standard for XML distribution of information. It started as an update to Really Simple Syndication (RSS), and, thanks in part to the use of RSS in the blogging community, took on a life of its own as a general information distribution medium.<\/p>\n

One part of the Atom standard is AtomPub, a RESTful<\/a> way to publish Atom feeds. The atomserver implements AtomPub, in Java, and along with a demo installation that’s easy to set up and use.<\/p>\n

I’ll post more as I discover ways to use this.<\/p>\n<\/div>\n

\n
\nTranslate<\/span><\/a>\"\"\n<\/div>\n","protected":false},"excerpt":{"rendered":"

I read the XML Daily Newslink, and saw the following reference: AtomServer Helps Serve Up AtomPub Taylor Cowan, O’Reilly Technical The most interesting development within the XML world of late is AtomPub. It abstracts the details (however simple they may be) of REST and provides them in a well specified protocol. Instead of writing home […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-495","post","type-post","status-publish","format-standard","hentry","category-computer"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p2w3Qj-7Z","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/posts\/495","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/comments?post=495"}],"version-history":[{"count":0,"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/posts\/495\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/media?parent=495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/categories?post=495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alephnaught.com\/Blog\/wp-json\/wp\/v2\/tags?post=495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}