[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [syndication] Re: ANN: RSS 'ping' interface at fyuze.com
JDKLUB, those are good points. Indeed -- there's no need for a name, since
the RSS feed tells you what its name is. On the other hand if the caller
sends you the name of the feed, then you don't have to read it to get its
name. But you're probably going to read it anyway to verify the change
otherwise you're going to get spammed. OK, so maybe it's a better fit for
the "SOAP Meets RSS" spec that's part of RSS 0.92. Dave
----- Original Message -----
From: "jdklub" <pseudonym@mindspring.com>
To: <syndication@yahoogroups.com>
Sent: Tuesday, July 02, 2002 8:13 AM
Subject: [syndication] Re: ANN: RSS 'ping' interface at fyuze.com
> --- In syndication@y..., "Bill Kearney" <wkearney99@h...> wrote:
> > > I can help thinking that it might have been better to just use
> > >the
> > > weblogs.com API. http://www.xmlrpc.com/weblogsCom
> >
> > Indeed, does this interface not support enough of the
> > functionality?
>
> in theory, the weblogs.com api does provide the functionality that
> is needed. however, the weblogs.com api accepts the url of a site
> (http://somesite.com) whereas the API at fyuze accepts the RSS feed
> for a site (http://somesite.com/rss.xml). i wanted to minimize the
> confusion.
>
> also, the weblogs.com api accepts two parameters, one of which is
> the name of the site, which i don't need and have no use for. it
> would be a clunky fit, and if i ever need to expand the api in any
> way (though i don't how i would need to for the ping method) i'm
> free to do it without breaking an implementation of the weblogs.com
> api, or my api (since it uses a struct with named members, instead
> of ordered parameters).
>
> i'm really just trying to minimize the confusion, and make it clear
> that it does not mirror the functionality of weblogs.com. (ie. don't
> ping it with your website url, ping it with your RSS url)
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>