<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 13, 2019, at 10:17 AM, Nikolaos Ves <<a href="mailto:vesnikos@gmail.com" class="">vesnikos@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:tahoma,sans-serif">I understand that it is a different conversation but i cannot stop to wonder that it would be also wasted effort if down the road the CDN providers ask for a reasonable amount of money to sustain their services when all proj users use their resources to fetch grid files. </div></div></div></blockquote><div><br class=""></div><div>Fair point. I would think an organization like OSGeo could step forward (especially after we complete OSGeo project incubation) to provide the resources to cover in that situation.</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:tahoma,sans-serif">Technically, I am still trying to cope with the build changes proj brought to some frameworks/libraries, so as long it's **optional**, hey it's good to have ;) </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Out of curiosity, is there any other project with similar approach as the one suggested?</div></div></blockquote><br class=""></div><div>Many, if not most, of the popular JavaScript libraries use CDNs as their primary distribution mechanism with the network and storage resources contributed by the CDNs themselves. The Python project uses Fastly, for example. I don't think we would be treading any new ground with the approach.</div><br class=""></body></html>