This framework was developed for NetNewsWire and is made available here for developers who just need the parsing code. It has no dependencies that aren’t provided by the system.
Update 6 Feb. 2018: RSParser is now a CocoaPod, with the much-appreciated help of Silver Fox. (We think it worked, anyway. Looked like it did.)
This framework includes parsers for:
- RSS, Atom, JSON Feed, and RSS-in-JSON
- OPML
- Internet dates
- HTML metadata and links
- HTML entities
It also includes Objective-C wrappers for libXML2’s XML SAX and HTML SAX parsers. You can write your own parsers on top of these.
This framework builds for macOS. It could be made to build for iOS also, but I haven’t gotten around to it yet.
To get the type of a feed, even with partial data, call FeedParser.feedType(parserData), which will return a FeedType.
To parse a feed, call FeedParser.parse(parserData), which will return a ParsedFeed. Also see related structs: ParsedAuthor, ParsedItem, ParsedAttachment, and ParsedHub.
You do not need to know the type of feed when calling FeedParser.parse — it will figure it out and use the correct concrete parser.
However, if you do want to use a concrete parser directly, see RSSInJSONParser, JSONFeedParser, RSSParser, and AtomParser.
(Note: if you want to write a feed reader app, please do! You have my blessing and encouragement. Let me know when it’s shipping so I can check it out.)
Call +[RSOPMLParser parseOPMLWithParserData:error:], which returns an RSOPMLDocument. See related objects: RSOPMLItem, RSOPMLAttributes, RSOPMLFeedSpecifier, and RSOPMLError.
Call RSDateWithString or RSDateWithBytes (see RSDateParser). These handle the common internet date formats. You don’t need to know which format.
To get an array of <a href=… links from from an HTML document, call +[RSHTMLLinkParser htmlLinksWithParserData:]. It returns an array of RSHTMLLink.
To parse the metadata in an HTML document, call +[RSHTMLMetadataParser HTMLMetadataWithParserData:]. It returns an RSHTMLMetadata object.
To write your own HTML parser, see RSSAXHTMLParser. The two parsers above can serve as examples.
When you have a string with things like — and ë and you want to turn those into the correct characters, call -[NSString rsparser_stringByDecodingHTMLEntities]. (See NSString+RSParser.h.)
If you need to parse some XML that isn’t RSS, Atom, or OPML, you can use RSSAXParser. Don’t subclass it — instead, create an RSSAXParserDelegate. See RSRSSParser, RSAtomParser, and RSOPMLParser as examples.
SAX is kind of a pain because of all the state you have to manage.
An alternative is to use NSXMLParser, which is event-driven like SAX. However, RSSAXParser was written to avoid allocating Objective-C objects except when absolutely needed. You’ll note use of things like memcp and strncmp.
Normally I avoid this kind of thing strenuously. I prefer to work at the highest level possible.
But my more-than-a-decade of experience parsing XML has led me to this solution, which — last time I checked, which was, admittedly, a few years ago — was not only fastest but also uses the least memory. (The two things are related, of course: creating objects is bad for performance, so this code attempts to do the minimum possible.)
All that low-level stuff is encapsulated, however. If you just want to parse one of the popular feed formats, see FeedParser, which makes it easy and Swift-y.
Everything here is thread-safe.
Everything’s pretty fast, too, so you probably could just use the main thread/queue. But it’s totally a-okay to use a non-serial background queue.