<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>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. </div><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><br><div>-----------------------<br>Garrick van Buren<br></div><div><a href="http://garrickvanburen.com">http://garrickvanburen.com</a><br>612 325 9110<br>-----------------------<br></div></span></div><br><br></span>
</div>
<br><div><div>On Oct 29, 2013, at 12:59 PM, vernon adams wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I’m not sure Quinn is after what you think he is :)<br><br>Quinn… do you mean you want to serve fonts like the example i am serving from <a href="http://newtypography.net/testing/">http://newtypography.net/testing/</a> ?<br><br>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?<br>A.k.a users can’t simply browse the css source and see that ‘myfont.ttf’ is residing at ‘<a href="http://myweb.com/fonts/myfont.ttf'">http://myweb.com/fonts/myfont.ttf'</a><br>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.<br><br>-v<br><br><br><br><br>On 29 Oct 2013, at 10:39, Dave Crossland <<a href="mailto:dave@lab6.com">dave@lab6.com</a>> wrote:<br><br><blockquote type="cite">On 29 October 2013 13:05, Quinn Keaveney <<a href="mailto:qkeave@gmail.com">qkeave@gmail.com</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">By saying I don't want to use @ff I just mean that I want to use an @ff that<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">obfuscates the link/src file so you can not just click and download the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">woff.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This is impossible.<br></blockquote><br></div></blockquote></div><br></body></html>