I haven't fig­ured this out com­plete­ly yet, but I got start­ed on writ­ing an Apache Wook­ie Con­nec­tor Frame­work in Perl. What it seems to do is get some wid­gets from a Wook­ie wid­get serv­er and set up the em­bed­ding in an HTML page. This isn't very in­ter­est­ing un­til you re­alise that HTML page could be the main screen on your phone or the desk­top on your net­book, and the Wook­ie serv­er some kind of app store. And the wid­gets aren't just some piece of HTML with CSS and JavaScript. The Wook­ie serv­er takes care of the same ori­gin pol­i­cy by pro­vid­ing a proxy API so the brows­er does all re­quests through the same ori­gin of the Wook­ie serv­er, and the Wook­ie serv­er does the ac­tu­al re­quests. But apart from re­ceiv­ing and send­ing data from and to oth­er ser­vices via HTTP the Wook­ie serv­er can also store data it­self. Based on API keys and user IDs wid­gets can store data re­lat­ed to a par­tic­u­lar wid­get be­long­ing to a par­tic­u­lar user in a par­tic­u­lar en­vi­ron­ment on the Wook­ie serv­er. And be­cause it's on the same serv­er wid­gets can also share data be­tween them, even be­tween dif­fer­ent users. Cur­rent­ly not ac­tu­al­ly in real time, but wid­gets can use the Wook­ie serv­er to com­mu­ni­cate be­tween them like in a chat wid­get that sends mes­sages to the Wook­ie serv­er and then re­ceives up­dates from oth­er wid­gets in the same chat ses­sion. And all that in an easy HTML + JavaScript en­vi­ron­ment, which was orig­i­nal­ly what I was try­ing to get in to.