You can in fact do this, it is a technique known as Super-Resolution and has been around for at least a decade. http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=5...

The most precise maps of Pluto were made with a similar technique: http://www.boulder.swri.edu/~buie/pluto/mapstory.html

That's really cool. I wonder if that could be used to get images of other planets.

gus_massa posted a link about Pluto:

http://www.boulder.swri.edu/~buie/pluto/mapstory.html

That's weird, I usually go the other way - I redirect the www to the naked domain.

I may be wrong here, but I think there's one good reason to use anything.example.com instead of example.com: with the naked domain, you can't have a separate domain for static assets which the client doesn't send the cookie to (for performance improvement). If you set a cookie with the domain example.com, it will still get sent to static.example.com.

Granted, you could use examplecdn.com or something, but then you have to register and manage more domains.

Isn't that what the domain portion of the set-cookie header is for?

It gets propagated to subdomains, it doesn't restrict it to just the domain specified.

Yes, it gets propogated to subdomains, but the point was that if you have subdomain X.y.z, as long as you set the cookie for y.z, the cookie is valid for X.y.z and U.y.z.

My point was that you don't want the cookie to be sent to other subdomains, so you'd actually want to set the domain to X.y.z. You can't do that if you're web domain is y.z.

Google AppEngine does not support naked domains unfortunately.

At least, that is what I use it for myself.

That's the way it should be. It's a shame the www convention took hold.

only reason www is usefull is because common cms (forums, blogs, comments, ....) convert www.example.com to a clickable link, but example.com not. yeah stupidbutthats the way it is.....

I don't understand why they would want to go grey when they are zooming in. They have the tile for the old zoomlevel, they should just scale it until new data comes in (and overlay the new data on the old). This is exactly what happens in the browser when you zoom (as long as you're not zooming, say, 6-7 levels).

Also, I think it would be better to render the whole page at once, with a width of something nominal like 800px or something, and then you can pan and zoom (with or without smart zoom) super fast in hardware. It has always been a dissapointment that the zooming is not as smooth on Android because the browser tries to re-flow all of the "fluid" pages to it's new width and height. (it also breaks some pages, where they try to float something to the bottom of the view, but the view on Android is just slightly larger than the screen, so it's unreachable)

Yes, you are right about the zoom. That's odd. Actually, when i zoom in on my Nexus One (with the control buttons, not pinch) it does scale the image until the new one appears.

And, no, please no. The way the browser adjusts the text width is really a nice thing! If you care about how your page looks like on a mobile device, do a mobile version ;)