You got it right Jeremy. I had meant -- "Will it be possible to use the Google Image search API, for content on the private side of a userID/ password ?"
Can you direct me to more detailed information about the 'robots.txt' or 'sitemap.xml' that you mention. Sorry, I did not understand the "TOS" acronym. thank you. Jeevan. On Jun 14, 7:54 am, Jeremy Geerdes <[email protected]> wrote: > I guess that I'm a bit confused what you're asking. If you're wanting to know > whether or not the TOS prohibit you from utilizing the API from an > application which is on the private side of a user/password site, then I > don't think that the TOS don't restrict you from utilizing the Image Search > API on a site that has username and password as long as obtaining those > credentials is free. But I'm not a legal expert, so you'll probably want to > consult someone who is. > > If you're asking if the API will index images which are available only on the > private side of a user/password site, then I think I remember reading > somewhere that you could provide Google with a username/password via the > robots.txt or something, but I'm not putting my finger on it right now. > Alternatively, you could use an Sitemap.xml file to highlight the images that > you want Google to crawl so that it can just bypass the user/password gateway. > > All of that said, I would be remiss if I did not advise you that the Image > Search API has been deprecated. This means that Google is no longer actively > developing new features, and while they will put some effort into making sure > that the service continues to operate, they reserve the right to terminate it > at any time should such efforts become "burdensome." In addition, the > deprecation policy states that the service will be discontinued no later than > three years after the announcement of deprecation. The announcement, in the > case of the Image Search API, came in May 2011. So you can expect that the > API will cease functioning no later than May 2014. > > Of course, if you don't mind developing an application today that won't work > in less than three years, you can just disregard that insight. But if I was > you, I would seriously think two or three times before I built an app on a > platform that I knew wasn't going to be around. > > Jeremy R. Geerdes > Generally Cool Guy > Des Moines, IA > > For more information or a project quote: > [email protected] > > If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > Church! > > On Jun 13, 2011, at 12:14 PM,g1wrote: > > > > > Hi, > > > I am trying out this Google API. > > > I see, that the google search api, can be restricted to search only a > > particular web site. > > But what are the pre-requisittes of such a searchable web-site ? > > > I guess, one of it would be ... the web site muct be publicly > > accessible !! > > > Can it be a protected by user-name/ password ? > > If yes, how can google api, be leveraged ? > > > thank you > >G1 > > > -- > > 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 > > athttp://groups.google.com/group/google-ajax-search-api?hl=en.- Hide quoted > > text - > > - Show quoted text - -- 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.
