Nice. Thanks, - Ed On Wed, Oct 12, 2011 at 12:35 PM, Nicolas Antoniazzi < [email protected]> wrote:
> > The main problem will be Search Engine. You will have to rely on htmlunit >> to >> > fix it (generates static version of webpages). >> >> The search engine result isn't important. >> What do you main by "htmlUnit to fix it"? >> > > HtmlUnit is a tool that embed a browser (firefox) and can execute > javascript code to produce an html output. It allows you to write website in > Javascript/Ajax and give something to parse to search engine which are not > able to parse javascript > > > http://code.google.com/intl/fr-FR/web/ajaxcrawling/docs/getting-started.html > http://code.google.com/intl/fr-FR/web/ajaxcrawling/docs/html-snapshot.html > > >> >> > you can still optimize it by including the javascript content inside >> your >> > html/jsp/php page. You can use code splitting to improve it too. >> >> What do you mean by "putting javascript in the html page directly"? >> Isn't gwt bootstrapping already directly contained in html and in >> control of loading all the resources as such that you have to wait >> till gwt performed all the bootstrapping through his own js files... >> > > It is only to avoid an extra round trip. A typical scenario is : > 1 - Client -> Get HTML index Page (with <scipt src="module.nocache.js" ... > inside) (Connection 1) > 2 - Client parse the html page and get the Javascript (module.nocache.js) > (Connection 2) > 3 - Client parse and execute the javascript (bootstrap) > 4 - Client detects browser version and retrieve correct module from server > (EAZKJ23A123131.cache.js) (Connection 3) > 5 - Your module will certainly need to get some data to display from the > server with an RPC request (Connection 4) > > You can optimize two connection from this scenario : > Step 1 : Instead of referencing an external javascript (module.nocache.js), > directly include the js content in you html page (easy to do with jsp) > Step 5 : All data dedicated to the first page can directy be included > inside the html page too. You can then read those informations with JSON > instead of doing a new RPC call. > > > > >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
