RE: 1+2) Yes, I think the less transactions the better for creating dynamic links on the client side.
RE 2) Multiple books in a single request is a tricky requirement because there needs to be a way to determine which book came from what submitted criteria. Google's API nests the results, but they only allow an identifier search at this time.
RE: 1+2) Yes, I think the less transactions the better for creating dynamic links on the client side.
RE 2) Multiple books in a single request is a tricky requirement because there needs to be a way to determine which book came from what submitted criteria. Google's API nests the results, but they only allow an identifier search at this time.
http:// books.google. com/books? bibkeys= ISBN:9780689317 804,LCCN: 2007004478& jscmd=viewapi
RE 3) I like this approach. Would it then be possible to limit search results by scanned books?
RE 4) Sounds interesting, I'd have to think about it. But I don't have a use case for this right now.
RE 5) Offset and Row options would be a good way to handle large sets.