atom-feed

I have subscribed my server to my Youtube channel via youtube PubSubHubbub. I am experiencing delay in notifications sometimes. Is there anyway ( like statistics, tracking, youtube API ) by which I can know, when the PubSubHubbub event is fired, so that I can actually know, if there is a delay? . The atom feed looks like this: <entry> <id>yt:video:vidxxx</id> <yt:videoId>videxxx</yt:videoId> <yt:channelId>channelxxx</yt:channelId> <title> titlexxx</title> <link rel="alternate" href="https://www.youtube.com/watch?v=vidxxx"/> <author> <name>Author</name> <uri> https://www.youtube.com/channel

We're trying to get 2-legged OAuth to work with the Gmail atom feed. We're using the Java library contributed by John Kristian, Praveen Alavilli and Dirk Balfanz. [ http://oauth.net/code/] instead of the GData library. We know we have the correct CONSUMER_KEY and CONSUMER_SECRET, etc. becuase it works with the Contacts feed ( http://www.google.com/m8/feeds/contacts/default/full ) and have no problems. However with Gmail atom feed it always returns: HTTP/1.1 401 Unauthorized Any ideas? Should we try a different OAuth framework or does the problem lie on the Google side? We think we got it

I'm writing a Lua application that generates an Atom feed. Right now, I'm generating XML "by hand" -- writing strings to files. This doesn't seem like the best way, although it may be. I am getting nervous about having the escaping exactly right. Has anyone done anything like this in Lua before? Should I stick with generating "by hand"? Or write a wrapper for an existing C library? (Perl, by comparison, seems to have a plethora of options .) I've generated XML by hand too. I created an API that looks like: function XmlElement(tag, text, attr) ... end function XmlSubelement(root, tag, text,

We're breaking a logical feed up over several physical feeds using the "next-archive" and "prev-archive" link relations to tie everything together. Should each individual feed have its own id, or should the id be constant across the whole series of physical feeds? The Atom specification says: 4.2.6. The "atom:id" Element The "atom:id" element conveys a permanent, universally unique identifier for an entry or feed. The ID for an entry should be the same across the different feeds it appears in. From the Atom discussion wiki : Restricting the uniqueness scope of atom:id entirely to a single feed

I'm trying to find a library that can read a given RSS/Atom feed, and that can guess its format and abstract it as a list of items. The idea is to build a simple RSS reader that could take any feed. I know PHP has a few libraries doing just that, but I can't find any .Net version. I believe the ASP.NET RSS Toolkit does what you want. If you are using 3.5 you can use classes from the System.ServiceModel.Syndication namespace Argotic is a pretty comprehensive content syndication framework. 来源： https://stackoverflow.com/questions/824949/rss-atom-parsing-library-for-net

Every book on REST uses <atom:link href="..." rel="..."> to define Hypermedia in RESTful apps; but Jersey ( with the use of JAXB ) do not seems to have this support. I've tried @XmlSchema in package-info.java as explained here ; I've also tried extending NamespacePrefixMapper as explained there . But none works and output this at best: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <customer xmlns:ns2="http://www.w3.org/2005/Atom"> <first-name>Roland</first-name> <ns2:link href="/customer/1" rel="self" /> </customer> Using namespace and, as a result, Atom, seems impossible in Jersey.

My website has an Atom feed and I want to make it easier to subscribe to it. I see that many sites such as StackOverflow have the Atom icon in the location bar in Firefox 3. I haven't, however, been able to work out how. I assume some HTML is needed - but what tags specify the the browser that a page has a feed? While the code provided in (all!) the other answers is absolutely correct, I would recommend against giving your feed a title of "RSS" if the format used is actually Atom. RSS, of course, refers to an entirely separate format for feeds and syndication and there's enough confusion among