Aleady explained what you need to do. I really wouldn't cache the search results and share them, for a couple of reasons:
1. It makes the application harder to use. If the user already knows, say, the ISBN of the book and wants to go directly to its page, then they couldn't unless it had been searched for first (because your shared list wouldn't contain it, of course).
2. It makes the application more complex, because you'd have to worry about the data in the cache being stale and refreshing them. Maybe the risk for this small app is minimal, but I think simpler is better right now.
Just do a query in the handler for the book page. It's not like the performance is going to be bad.
1. It makes the application harder to use. If the user already knows, say, the ISBN of the book and wants to go directly to its page, then they couldn't unless it had been searched for first (because your shared list wouldn't contain it, of course).
2. It makes the application more complex, because you'd have to worry about the data in the cache being stale and refreshing them. Maybe the risk for this small app is minimal, but I think simpler is better right now.
Just do a query in the handler for the book page. It's not like the performance is going to be bad.