The Dojo <a href="http://svn.xantus.org/shortbus/trunk/bayeux/protocol.txt">Bayeux</a> client implements a bunch of different "transports" and tries to pick the right one based on what the browser can support, the cross-domain requirements, and so forth. What follows is one of those stories that makes people assume that I'm crazy to do what I do for a living. They might be right.
If you're trying to do professional web development and you're running multiple versions of IE with one of the various hacks that's been making the rounds, it's going to bite you in the ass eventually. Here's a rundown of my toolchain and why virtualization is the only thing professionals should be using.
Sun looks set to squander its platform win. But it's not a done deal just yet.
On why Foo Camp really is all that.
I've just spent the last 4 hours wrangling Nokia's S60 and Microsoft's WinCE...erm...PocketPC...uh...Windows Mobile emulators into compliance. What have I learned? That not only do the carriers hate your guts, so do their tool vendors.
Cross-domain request-response via JSONP is pretty well understood these days. Well, at least among the 10 people who care. With Cometd we're taking it one level further.
The deluge is starting. Duck!
It's about the apps. Duh. But when the web is the platform, "cross platform" means "cross browser". ajaxWrite misses the point. By a country mile.
Back when I did security for a living, one of the hard problems that I was introduced to was that of taxonomy for describing difficult technical issues. Common language allows us to quickly talk about things and in the best case can improve accuracy in discussions. Obviously that's just best case. We need a common description for low-latency data transfer. I propose "Comet".
Amongst professional DHTML developers, the phrase "IE7" tends to draw more eye-rolls and quiet swearing than anticipation or excitement. Here's a short list of hard problems the IE 7 team will need to solve in order to stem IE's perception as the new boat-anchor browser.