The JSAPI (aka, Google Loader) was quietly orphaned several months before
the AJAX APIs were deprecated. It's now been well more than 3 years since
the APIs were deprecated. All this to say that you should be looking for an
alternative to the JSAPI, and I doubt you can expect any real response from
Google on this issue.

And even if you did get a response, the "bugs" you pointed out were
intentional parts of the design of the loader. In order to maximize
performance, the actual APIs that the JSAPI was intended to load were
designed to be cached for very long periods of time. This had the side
effect that, when an update to an API was pushed, it might be a very long
time before a browser would actually discover it unless the URL changed
with every update. These URL changes would then be pushed into the JSAPI.
Since the JSAPI was designed as a single entrance for many APIs, and
because each API was developed by a different team with its own deployment
schedule, URLs were changing on a fairly regular basis. So the JSAPI was
given a short cache life so that all users would be using the latest
version of an API within an hour or so of a push.

jg



On Sat, Jun 20, 2015 at 1:31 AM, Kapil Bhagchandani <[email protected]>
wrote:

> It seems like it is reported almost 4 years ago but no workaround is done
> yet.I would like to up-vote for this to be achieved.
>
> On Wednesday, 23 March 2011 20:29:36 UTC+5:30, James Cridland wrote:
>>
>> Hello there,
>>
>> Using Google Page Speed's tool, I notice that the jsapi call to the
>> Google Loader could be rather faster.
>>
>> Notably...
>>
>>
>>    - It is missing a cache validator. Resources that do not specify a
>>    cache validator cannot be refreshed efficiently. Specify a Last-Modified 
>> or
>>    ETag header to enable cache validation
>>    - It has a short freshness lifetime of just one hour. PageSpeed
>>    recommends specifying an expiration at least one week in the future.
>>
>>
>> Any chance of a fiddle?
>>
>  --
> --
> You received this message because you are subscribed to the Google
> Groups "Google AJAX APIs" group.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> To view this message on the web, visit
>
> https://groups.google.com/d/msgid/google-ajax-search-api/f22fd43a-c386-4ae5-9b23-6045afb6439b%40googlegroups.com
> <https://groups.google.com/d/msgid/google-ajax-search-api/f22fd43a-c386-4ae5-9b23-6045afb6439b%40googlegroups.com?utm_medium=email&utm_source=footer>
> For more options, visit this group at
> http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Google AJAX APIs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan
Church!
http://www.debraheightswesleyan.org

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
To view this message on the web, visit
https://groups.google.com/d/msgid/google-ajax-search-api/CAF4cwg-bKNNu%2BOv974SaDLJHBrMQ413K8rj9mm82LwiqyiVrkA%40mail.gmail.com
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to