Skip to content
This repository has been archived by the owner on Jan 2, 2021. It is now read-only.

Prepare code to use multiple search engines #9

Closed
brainkiller opened this issue Sep 14, 2012 · 1 comment
Closed

Prepare code to use multiple search engines #9

brainkiller opened this issue Sep 14, 2012 · 1 comment

Comments

@brainkiller
Copy link

The current search and update engine comicvine.com doesn't contain all prefered commics. Therefore it would be nice if other search engines could be used. Preparing the code for this will facilitate the implementation later on.This will also make it possible for other users to write search engines on their on without major code changes.

Possible future search engine once the API is implemented: http://www.comics.org/

@evilhero
Copy link
Owner

It actually compares CV agaisnt gcd (comics.org) in order to validate the information. Comicvine has information that gcd just doesn't have, and gcd doesn't have an api like comicvine does already.Web parsing on its own isn't a valid way to get primary data for this type of app as parsing in itself isn't reliable. I use it as a secondary in order to get detail info that would create too many api hits on comicvine. As far as I'm aware, comicvine contains a great majority of the comics.

Right now, this is a far away dream - I'm still refining and updating the code so who knows but unless there is some major hitch or problem, I don't think I'll be relying on webparsing alone to populate the data. Maybe if GCD would finally create an api themselves then we'd be in busness a lot easier. There was abit of talk about having one rollback vs the other but the tracking number would then be off as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants