On Fri, Oct 2, 2009 at 9:15 AM, Martin Higham <[email protected]> wrote: [snip] > Status Net should use relative URLs where possible. Given the high number of links and images within a page this will significantly reduce page sizes.
Just wanted to break this thread out as I was going to ask about this -- what's the historical reason for storing full URLs in the database for user profiles, avatars, etc? In addition to general output bloat I've found this problematic in some specific circumstances: * Visitng the site via https://identi.ca doesn't act as expected; you'll be shoved back to unencrypted http: when you follow any link. * When changing base hostname or URL path of a site, you need to fix up existing URLs in the database; this is an extra burden which is most likely to strike newbie admins when they're finalizing a site configuration. The HTML size savings of relative links are much smaller after gzipping, but this may make a bigger difference for mobile devices where memory and CPU may be extremely limited. -- brion
_______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
