Hi Chad,

I've tried to reproduce this behavior and have as of yet been unable
to. If the Ajax loader is added to the page using an HTTPS URL, then
the call to add the stats image should not be attempted. Are you
including the common loader using:

https://www.google.com/jsapi

If so, could I see your application to try to reproduce?

Thank you,

Jeff

On Oct 9, 1:55 pm, "Jeff S (Google)" <[email protected]> wrote:
> Hi Chad,
>
> The search control does require some of the features present in the
> Ajax loader, so I don't think there is an easy workaround. I'll keep
> you posted with what I find later today.
>
> Thank you,
>
> Jeff
>
> On Oct 9, 8:19 am, Chad <[email protected]> wrote:
>
> > You say:
>
> > "If you don’t want these requests to happen, you can include the
> > libraries directly instead of through the loader.  The direct links
> > are all listed 
> > here:http://code.google.com/apis/ajaxlibs/documentation/#AjaxLibraries";
>
> > Yet, I don't see "search" available on that page.  On our 
> > sitehttp://www.yinyanghouse.com/theajax search element is breaking our
> > ssl pages (the shopping cart checkout page).  If the page before the
> > person checks out has the ajax search box on it, this graphic is
> > loaded and flags an error in firefox and opera (possibly other
> > browsers as well).
>
> > I need to know how to not have this 1 pixel graphic loaded to avoid
> > this issue (or to get it loaded via https).
>
> > A brief code sample would be most appreciated....
>
> > On Sep 10, 9:22 pm, "Jeff S (Google)" <[email protected]> wrote:
>
> > > Hi Paul,
>
> > > Good question! Because many loads of the libraries are cached, we
> > > never see requests for them.  In order to better estimate our traffic,
> > > we use this request to inform us what has been loaded. Also, the
> > > request happens asynchronously much after the page loads so that we
> > > don’t slow down the application performance. These signals are used by
> > > us for capacity planning purposes. We have expanded some of our
> > > operations and grown our capacity. The signals we get from these logs
> > > are directly responsible for our ability to meet the needs of the
> > > community and help ensure global, low latency access to the system.
> > > For example, when a new library is released, we tend to see a traffic
> > > spike as we serve new and not yet cached versions of these libraries.
> > > Without information on how often these libraries are being requested
> > > from us, we have a more difficult time anticipating how large this
> > > spike might be.
>
> > > If you don’t want these requests to happen, you can include the
> > > libraries directly instead of through the loader.  The direct links
> > > are all listed 
> > > here:http://code.google.com/apis/ajaxlibs/documentation/#AjaxLibraries
>
> > > Happy coding,
>
> > > Jeff
>
> > > On Sep 7, 3:33 am, Paul Thomas <[email protected]> wrote:
>
> > > > Hi
>
> > > > I'm currently trying out the google hosted versions of jQuery.  It's
> > > > great to be able to use the libraries from google's servers, so
> > > > thanks.
>
> > > > I have noticed when I've been debugging my AJAX however that extra
> > > > calls appear to be being made to google's servers after the library
> > > > has already been downloaded.  These URLs look like the following:
>
> > > >http://www.google.com/uds/stats?r0=el%7Cjquery&nc=1252319019940_15016
>
> > > > They come from an image that is being embedded into the DOM,
> > > > presumably by some google javascript.
>
> > > > What is the purpose of these extra calls?  Is google monitoring sites
> > > > that use the hosted APIs?  If so what data is being collected and what
> > > > is it being used for?
>
>
--~--~---------~--~----~------------~-------~--~----~
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]
For more options, visit this group at 
http://groups.google.com/group/google-ajax-search-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to