Something to note: From a performance perspective, most lag is caused by setting up the HTTP connection. Essentially, anything other than Apache/Nginx/etc serving a static file (just like js/jpg/png/etc) on the same files system as the webpage itself will degrade delivery performance. Yes, cache headers can eliminate this issue for subsequent loads - assuming your site is someplace people will visit repeatedly within the cache lifetime.
----------------------- Garrick van Buren http://garrickvanburen.com 612 325 9110 ----------------------- On Oct 29, 2013, at 12:59 PM, vernon adams wrote: > I’m not sure Quinn is after what you think he is :) > > Quinn… do you mean you want to serve fonts like the example i am serving from > http://newtypography.net/testing/ ? > > A.k.a you want your fonts to be served to remote web pages by simply adding a > 'link href’ line to the head of the source html document and then using the > ‘font-family’ to set text ? You (or anyone else using your webfont) would not > have to write those lines and lines of @font-face rules in css documents? > A.k.a users can’t simply browse the css source and see that ‘myfont.ttf’ is > residing at ‘http://myweb.com/fonts/myfont.ttf' > Of course, even if you use a ‘server’, people can still download the fonts, > e.g. by using Chrome's ‘Developer Tools -> Elements’ and grabbing the woff > files of any fonts embedded in the page. > > -v > > > > > On 29 Oct 2013, at 10:39, Dave Crossland <[email protected]> wrote: > >> On 29 October 2013 13:05, Quinn Keaveney <[email protected]> wrote: >>> By saying I don't want to use @ff I just mean that I want to use an @ff that >>> obfuscates the link/src file so you can not just click and download the >>> woff. >> >> This is impossible. >
