> That's the whole idea of DataResource - you can set aggressive cache headers
> to reduce the load on your servers.

But another feature I don't like about this is, that when you save the
file, it has a strange name. And the file with data: uri even
stranger, different each time you save it (e.g. Oo0X7cbg.pdf.part, not
even with PDF extension). I use only ImageResources, primarily because
many images are loaded in a single larger one. I achieve the caching
thing of downloaded documents by adding ?hash=xxxxx to the URL. The
resource is statically placed on the web root directory and the HTTP
server will serve it from there ignoring characters after the question
marks - these are for browser to know that it is a different file when
caching is enabled. After save, the file is named without the question
mark and characters after it.

And secondly, the data:uri is optimization not needed in this use
case: suppose you have hundreds of documents that the GWT compiler
decides to inline as data: URI. The script will get very large, will
have to be downloaded, but only few users will actually need to view
the document. And after recompile, another large script will be
downloaded. If you used the approach I mentioned above, their hash
will not change during each compile and will not be downloaded at all,
if the user does not click that link. Inlining is good, if the user
accesses that resource in most use case scenarios.

> IE8 has the 32KB limit on data:uri .. may be thats the issue. Or perhaps
> some PDF renderers don't understand data:uri.

This particular file has 44kB, and all other there have over 32kB.
Maybe, Hendrik, you should test with smaller PDF if it works in IE.

> I also looked at the code and couldn't find a way to disable inlining of
> DataResource. I tend to agree its a bug..

-- 
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.

Reply via email to