Hi String,

The content-rewriter should remove the need to do that since it will
attempt (when it's turned on at least) to cache external JS
automatically. I believe this is the feature being employed by MyAOL,
which is also using a Shindig-based gadget renderer, if I recall
correctly.

Dan

On Jun 25, 6:53 pm, String <[email protected]> wrote:
> On Jun 26, 1:20 am, "Dan (Google)" <[email protected]> wrote:
>
> > Are your gadgets doing document.write (or those of anyone else
> > experiencing this issue)?
>
> Hi Dan,
>
> Sounds like a good hypothesis. Yes, I use document.write quite
> extensively in my gadgets, to enable partitioning of my JS source into
> manageable units while still leveraging the IG cache. Like this
>
> document.write('<script type="text/javascript" src="' +
>   _IG_GetCachedUrl('http://www.example.com/sourcefile.js') + '"><\/
> script>');
>
> I know there are a few containers (like MyAOL, I think) that parse
> <script> tags out of the gadget source and cache them automatically;
> if this was supported more widely I wouldn't do it myself. But for
> now, the above approach has been invaluable, especially for external
> libraries (common in map gadgets) that it's impractical to include
> inline.
>
> String
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" 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-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to