- From: Sergey Malkin <sergeym@microsoft.com>
- Date: Wed, 5 May 2010 13:35:26 +0000
- To: Dave Crossland <dave@lab6.com>, Ben Weiner <ben@readingtype.org.uk>
- CC: "www-font@w3.org" <www-font@w3.org>, Sylvain Galineau <sylvaing@microsoft.com>
> Why are fonts different than any other resource on the web? Meaning, why do we need an update mechanism different from the regular update mechanisms (cache headers, etc.)? I think regular mechanisms will work for fonts just fine, maybe even better. Once new version is served to a user, UA will download new version. Interesting things happen between font services and website. Services like TypeKit are able to serve exactly the version web designers tested their site with. Site owner will receive notification that new version is available, e.g. by e-mail, and once site is tested with updated font, administrator tells font service to start sending new version to site visitors. It is not even client-side minimal requirement, everything is taken care of by site servicing fonts. No need to even update stylesheets. Whole range of options is available: exact build number, particular major version, equal or greater version, or always use latest version available. These options may have different price marks too. Thanks, Sergey
Received on Wednesday, 5 May 2010 13:36:56 UTC