This post originated from an RSS feed registered with Java Buzz
by Russell Beattie.
Original Post: UAProfs
Feed Title: Russell Beattie Notebook
Feed URL: http://www.russellbeattie.com/notebook/rss.jsp?q=java,code,mobile
Feed Description: My online notebook with thoughts, comments, links and more.
I like WURFL, but I also very much like the idea of the manufacturers themselves keeping their own handset profile XML files up to date. I ran across this again while looking at a Nokia XHTML-MP document and did a Google and found this great UAProf resource over at Source02:
These sites seem very up to date. Here's an example of Nokia's 7610 profile document. It's in RDF (urgh) but it seems quite complete and very accurate. I know that Cocoon uses DELI, and I know that Cocoon is used in production at Vodafone and other big mobile carriers, so this is something to take seriously. The combination of real-world usage and the fact that the manufacturers themselves are maintaining these documents is really quite compelling, no?
Now the question is, "How do you use these damn things efficiently?" Think about a website getting hammered by thousands of handsets per minute. I'm going to have to have some big-honkin data-structure in memory and check against it for every request - or at least per session. It seems like a great way to slow your mobile website down to a crawl. I guess I'll have to look at how Cocoon uses DELI and see if there's any secrets to learn there.
Previous Topic
