Hi omr and Vision, Although the Custom Search element is built on the legacy Search Control, there are no plans to deprecate or quota it. Eventually, we'll probably move from the old API to the new one under the covers, but this won't affect existing users.
As for the question of keys, they are not required for the Custom Search element (or for any of the old style APIs). As part of the documentation rewrite, we took a firmer stance on the usage of these optional keys, in order to more strongly encourage developers to use them. One reason for this is that developers who use keys are less likely to be incorrectly identified as misusing the API. Therefore, by using strong wording to increase key usage among new developers, the intent is to help make sure they don't run into problems later. But rest assured that no implementations of the Custom Search element should be hitting usage limits or stop working for lack of key. Of course, no one is perfect, so if you *do* detect any odd behavior, please post to the forum and we'll look into it ASAP. Thanks, Adam On Nov 5, 10:44 am, Vision Jinx <[email protected]> wrote: > Hey Omr, > > Thanks for bringing up these questions and I am sure Adam will also > provide a response as well, but my current understanding on this is > that it should still work with out a key but will be greatly limited > in the number of queries it's able to perform (as they tighten their > enforcement rules). ie. intended for development as keyless. As for > that particular API/feature I am still not sure myself exactly what > limits are going to be placed on it and when, but I believe there is a > bit of a grace period but am sure that will be rate limited soon as > well. > > Regards, > Vision Jinx > > On Nov 5, 7:17 am, omr <[email protected]> wrote: > > > > > > > > >http://code.google.com/apis/customsearch/docs/js/cselement-devguide.html > > > > "... Warning: You need your own API key in order to use the Custom Search > > > element. ..." > > > What fate awaits site owners who have obtained Custom Search / Site > > Search code from the existing CSE wizard and control panel (which > > still provide code to use the Custom Search Element / > > CustomSearchControl WITHOUT a key)? > > > Will new restrictions be imposed on all sites that use 'keyless' > > code? Will owners of all such sites be advised to obtain and apply > > keys in order to restore normal operation? > > > Alternatively could those sites using the Search Element without a key > > be permitted to continue operating exactly as before (without any new > > restrictions due to the lack of a key)? > > > If the latter is true, why are we 'warned' unequivocally that we > > "need" a key in order to use the Custom Search Element? Further, why > > are we advised that code "won't work" without a key? At the present > > time the CustomSearchControl remains operable without a key. Are new > > restrictions already in place for keyless usage, or are such > > restrictions scheduled to be imposed? > > > Thanks > > > -- omr -- 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.
