Using XPath as a yardstick, what's so complex about this?
/atom:feed/atom:entry[1]/atom:[EMAIL PROTECTED]'HTML'|@type='TEXT'][0]
I'm not even sure how I'd approach choosing between HTML and text in the current approach, where one is in atom:content and the other is referred to by atom:link; I'd need to use XSLT, I suspect.
If your software only wants to live in a world where entries have only one type of content, it's maybe a few lines of extra code to choose one, and no change to the database. Atom doesn't require you to persist all of the entry.
On Feb 1, 2005, at 7:47 AM, Graham wrote:
On 31 Jan 2005, at 7:02 pm, Mark Nottingham wrote:
If the concern about multiple content is solely that it will result in more bandwidth use, I think it's misplaced; people who are concerned about bandwidth won't publish multiple representations inline; forcing them not to by legislation is misguided.
It's the implementation costs at the client. If you allow multiple content of the same mime-type, even minimal software has to have a significantly more complicated interface to allow users to choose which one to show, and a significantly more complex database to make it happen.
Big fat -1.
Graham
-- Mark Nottingham http://www.mnot.net/
