Thanks for the reply! I took a look at what your saying about NodeID and I understand a bit more clearly now. Wow the Pub/Sub spec is large! Anyways. I'm thinking of writing a service where users can "subscribe" to feeds off the web. A service will be monitoring all "feeds" and pulling the RSS/Atom/whatever off of the web and populating the Pub/Sub nodes in batch so users get notifications. So really the service will create the new node to represent the news feed if its not already found in the Pub/Sub query and then add it to its "queue" of feeds to poll. I'm not quite sure what XEP to use to allow a user to "request" pulling of a feed. I haven't figured that part out yet. I'm also not sure if I want to mix Atom nodes with RSS nodes etc. I could create 1 format to use for the "entry" and transform them to all match but for sites which add extra metadata to entries such as Digg with its DiggCount I would like to maintain that. That is the beauty of XML :) That way Jabber clients who understand extensible items can display them. I like the idea of the NodeID being the feeds url because then this "polling" service can use the feeds URL easily as the SET after downloading content. Any suggestions / recommendations would be great to hear!Another item I am unclear about is as I am polling for news data, how can I easily check if an "entry" exists already? I'd rather not have to keep a cache somewhere of all the items I have created already. Although performance is going to suck if I have to check every entry before inserting. Is there a way to batch insert, and disallow duplicate entries based on *something* like entry title or something? It's nice to be back in Jabber land :) I'm back into the old mindset where I have a ZILLION ideas rushing into my head about all the crazy things I can do with these XEPs lol. Any help would be great! Thanks so much!
> Date: Wed, 21 May 2008 21:11:43 -0600> From: [EMAIL PROTECTED]> To: > [email protected]> Subject: Re: [Standards] Pub/Sub & RSS> > On 05/21/2008 > 6:26 PM, Kelly S wrote:> > > > Hi all. I am just getting back into XMPP after > a few years away from> > it and I am digging into the Pub/Sub XEP. I am > looking for a bit of> > feedback. I am writting the service which will pull > data from RSS and> > "publish" it via Jabber. However I need a way to relate > the unique> > RSS url to the XMPP pub/sub name so that I know where to store > these> > every time. In the leaf node would I place the RSS url in the <item> > > node="">? This doesn't sound too intuitive because I imagine some> > > Pub/Sub "browsers" use this as the node name, is this correct? This> > would > look ugly if you had http://www.site.com/rss.xml and 100's of> > others in > there lol. I don't think the nodename necessarily needs to> > be the unique > identifier. I'm sure I am just understanding wrong :)> > Any clarification > would be great! Thanks! > > The NodeID are opaque. You can make them whatever > you want. If it's> easiest for you to make them the same as your RSS feed > URLs, go for it.> > Just curious: what flavor of RSS are you using? Are you > indeed sending> RSS over XMPP, or are you sending Atom instead?> > Peter> > > -- > Peter Saint-Andre> https://stpeter.im/> _________________________________________________________________ Try Chicktionary, a game that tests how many words you can form from the letters given. Find this and more puzzles at Live Search Games! http://g.msn.ca/ca55/207
