Hot refactor

Went back and fixed quoting on collection and search which I forgot to do in the last pushes.  Sorry about that :)
Oh, that is a much better idea... damn why didn't I think of that.  Guess I was to wrapped up in calls to bgg.

So in my example, I pull a user, which then has buddies, and each buddy is a user object, not just a string.  Then if I want info on that buddy's collection, then I could call the user.collection, which will use the name it already has to fetch the collection without the actual user fetch.

I think that having the request objects and results objects are still a good design.  Requests objects know how to get the data, result objects store the data.

Let me give this some thought. :)

Thanks for the awesome insight!