No subject

Fri Aug 3 19:33:07 CDT 2007

eople start subscribing to it.
=20
I'm not sure how to handle the user requesting a new feed that doesn't exis=
t yet so that we can start pulling/publishing it.
> > 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 m=
atch 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 =
:)> > But RSS isn't XML. :P>=20
=20
RSS isn't XML? I'm not sure what you mean lol. Are they not exposed as XML =
documents? lol.
> > 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.> > Sure. :)> > > Any suggestions / recommendations wo=
uld 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 create=
d already.> > > > Although performance is going to suck if I have to check =
every entry> > before inserting. Is there a way to batch insert, and disall=
ow> > 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 mi=
ndset> > where I have a ZILLION ideas rushing into my head about all the cr=
azy> > things I can do with these XEPs lol.> > > > Any help would be great!=
> > > > Thanks so much!> > You might want to join this list for discussion:=
> > http://mail.jabber.org/mailman/listinfo/social> > "XMPP and Social Netw=
orking, Two Great Tastes That Taste Great Together!"> > /psa>=20
Also a bunch of concerns pop into my head that I'm still unclear about when=
 maintaining all this "feed" data.
=20
1. Is there any way I can just publish the latest feeds I pulled down and p=
ubsub discard any duplicates that may already exist? Or is the right way to=
 handle this is to query every single entry individually to check if they e=
xist before publishing them?
=20
1.a If I have to query each individually. Would I make the entry id the url=
 of the entry so that I can check for duplicates as I pull them down off th=
e web and read the entries? (example 4 old entries, but 1 new entry since l=
ast pull).
=20
2. Entry requesting. Is there any sort of querying we can use against them?=
 If we are publishing tons of entries, someone may want to browse/read them=
 but only request X amount at a time, or only newer than a certain date etc=
. I don't think pulling the entire entry history of a couple months is goin=
g to be too efficient.
=20
Some of my concerns for #2 is because we are going to mobilize this, data p=
lans are expensive for mobile devices. In this country it can be $25/1.5MB/=
month.
=20
We want to try and make our mobile client query data efficiently but do the=
se capabilities exist in Pub/Sub?
=20
Thanks so much for the help :)
_________________________________________________________________

--_9479f705-1487-41c3-a307-7c373594960c_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
 &gt; Date: Thu, 22 May 2008 10:53:34 -0600 &gt; From: stpeter at st=
peter.im &gt; To: standards at xmpp.org &gt; Subject: Re: [Standards] Pu=
b/Sub &amp; RSS &gt; &gt; On 05/21/2008 10:09 PM, Kelly S wrote: =
&gt; &gt; Thanks for the reply! &gt; &gt; &gt; &gt; I took a look at=
 what your saying about NodeID and I understand a bit &gt; &gt; more cle=
arly now. Wow the Pub/Sub spec is large! &gt; &gt; Don't be afraid, =
it's just comprehensive. :) &gt; &gt; &gt; Anyways. I'm thinking of =
writing a service where users can &gt; &gt; "subscribe" to feeds off the=
 web. A service will be monitoring all &gt; &gt; "feeds" and pulling the=
 RSS/Atom/whatever off of the web and &gt; &gt; populating the Pub/Sub n=
odes in batch so users get notifications. &gt; &gt; &gt; &gt; So rea=
lly the service will create the new node to represent the news &gt; &gt;=
 feed if its not already found in the Pub/Sub query and then add it to &=
gt; &gt; its "queue" of feeds to poll. &gt; &gt; &gt; &gt; I'm not q=
uite sure what XEP to use to allow a user to "request" &gt; &gt; pulling=
 of a feed. I haven't figured that part out yet. &gt; &gt; You can r=
equest the items in a feed by using this: &gt; &gt; http://www.xmpp.=
org/extensions/xep-0060.html#subscriber-retrieve &gt; 
&nbsp; 
Sorry I don't think I explained too well. Users will be requesting to add f=
eeds to their account, which in turn will subscribe them to the correspondi=
ng pub/sub node. 
&nbsp; 
But if someone requests a feed we are not "publishing" we need to begin pub=
lishing that new feed and subscribe the user to it. 
&nbsp;