Bug 15015 - Convert search system to use google's XML protocol
Convert search system to use google's XML protocol
Status: CLOSED CURRENTRELEASE
Product: Red Hat Web Site
Classification: Red Hat
Component: Other (Show other bugs)
current
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Martin C. Messer
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-01 13:45 EDT by Paul Lindner
Modified: 2015-01-07 18:41 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-07-22 13:00:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Google's Site Search Results Document (41.29 KB, text/html)
2001-05-21 19:29 EDT, Tom Lancaster
no flags Details
Google's Websearch Results Document (41.07 KB, text/html)
2001-05-21 19:30 EDT, Tom Lancaster
no flags Details

  None (edit)
Description Paul Lindner 2000-08-01 13:45:47 EDT
We can finally ditch our little google parser for a standard XML parser

Let's change to this asap.
Comment 1 Jay Turner 2001-05-14 17:20:58 EDT
What's the status of this?  Can I close it?
Comment 2 Tom Lancaster 2001-05-21 18:51:36 EDT
This hasn't actually been done, as far as I'm aware. I've mailed Google to find
out what on earth their XML protocol is.
Comment 3 Tom Lancaster 2001-05-21 19:29:13 EDT
Created attachment 19210 [details]
Google's Site Search Results Document
Comment 4 Tom Lancaster 2001-05-21 19:30:04 EDT
Created attachment 19211 [details]
Google's Websearch Results Document
Comment 5 Tom Lancaster 2001-05-21 19:31:39 EDT
Added a couple of attachments which came from "Blake Bouldin" <blake@google.com> 

Will assess the benefits of using their XML protocol.
Comment 6 Jay Turner 2001-09-17 15:05:08 EDT
What's the status on this?
Comment 7 Martin C. Messer 2003-07-22 13:00:23 EDT
i'm assuming this is no longer an issue

Note You need to log in before you can comment on or make changes to this bug.