AWS4 and BrowseNodeLookup

[r2d2]

Im developing an AWS4 site for the US, and am planning on using the BrowseNodeLookup search to return all of the nodes child nodes, then an ItemSearch with the same nodeid to return 10 of the products in that node. Does anyone else do this?

I was concerned about the 1 query a second thing. Obviously two queries for one page is probably going to be within 1 second.

What does everyone else do?

[Chris]

Maybe store nodes locally and run a cron job nightly to look them up?

[moonshield]

how does one go about doing that? Storing them locally?

[Chris]

Make a database.

[r2d2]

Yes, that would be a good way to go - I'll see if I can code something up over the weekend.

[Blue Cat Buxton]

Ive ben thinking about how this works. Here is my logic

You do a call to Amazon then wait a second, and get the next chunk of data. You gat no more than 60 results a minute, 3600 per hour.

Each browse node can return say 100 pages each (on average) with 10 results, that is 100+ !00x10 for the data on each product.

xsay 10 products thats like 3 hours plus worth of requests to Amazon, to fill up the database.

Am I on track so far?

So do you need like 2 databases and swap them over, so one is always available whilst the other is being filled up?

Just trying to understand the process (ill think about the coding later!).

[r2d2]

What I meant was just for listing the child nodes of a node - not products at all. Still a lot of calls though.

[Blue Cat Buxton]

Ah ok, not quite so bad then

I haven't really looked at node lookup; Do the nodes change often enough to warrent a once a day lookup?

[moonshield]

do I have to worry if using the system on this site?

[Blue Cat Buxton]

Not is you are using cacheing