Okay, I think you might want to go here and use the Page speeding up process in the services. Now they are offering this to a limited number of webmasters but maybe you can register and get it done. The other option is CloudFlare, that's free and some statistics suggest it's faster. Check that out as well.
I was thinking doing a subdomain cdn.gamequeryjs.com where all the released javascript would be hosted and delivered through CouldFlare, what do you think ?
Ok it's set up ! In 24 hours it should be running on CloudFlare. I've wrote the site http://cdn.gamequeryjs.com/ with the explanations about how to use the CDN.
What do you think, is it understandable ?
As soon as it's stable I will link it from the main website and speak about it there too.
Infact if you could advise on helping the page load first and then the game, it would be good. Putting the jQuery and gameQuery imports at the end. Rather than in the head I mean.
Is this cdn process still active for gameQuery 0.7? Does it make a difference compared to calling the files locally off of our own web host? I guess I will test and find out...
Which remind me that the cdnjs hosted version is not updated ... I will try to submit the new version to them tomorrow.
If everyone uses the CDN then chances are that a given user will have the js already cached somewhere (of course gQ is not yet used widely enough to make this situation very probable). There is an advantage over using a version hosted on the normal gQ website since the CDN hosted one will be served through a geographically close server which will minimized the access time.
@Blackhawx The reason why CDNs exist is too speed up your application load time on client's system as the response time of your server/webhost might not be fast for some third person. Whereas CDN allows quick delivery of the content.
Comments
Either way this will help a lot!
Thanks
Which remind me that the cdnjs hosted version is not updated ... I will try to submit the new version to them tomorrow.
If everyone uses the CDN then chances are that a given user will have the js already cached somewhere (of course gQ is not yet used widely enough to make this situation very probable). There is an advantage over using a version hosted on the normal gQ website since the CDN hosted one will be served through a geographically close server which will minimized the access time.