Recently I’ve been working on integrating search functionality into nntp//rss. Syndic8.com offers up an XML-RPC API, and I thought that this would be a great way to integrate the search functionality. Feedster are also just about to release an XML-RPC API, and this too will be integrated into nntp//rss.
I’m using the syndic8.FindFeeds and syndic8.GetFeedInfo operations. FindFeeds allows you to initiate a search by supplying a search term. It returns a list of matching Feed Ids as its response. GetFeedInfo is used to retrieve the feed information, taking a list of Feed Ids as its input. It also allows you to narrow down the set of returned feed attributes, which enables optimization of the amount of data returned from Syndic8 to the XML-RPC client. Unfortunately the documentation did not seem to provide a list of the specific field names that could be specified, so, to help other people working with the API, I’ve listed below all the fields returned by GetFeedInfo.
My only current issue with the API is the fact that the FindFeeds function performs an unbounded search – I can’t seem limit it to a maximum number of results. If someone, for example, searches using the term ‘RSS’, they’ll get a list of over 15000 feed Ids. I’d like to be able to say ‘give me the first 200 matches’, which will not only result in a more compact response from Syndic8, but should also place less stress on their servers.