RE: [Rails-devel] TokenHolders

[Brett L. <wak...@ea...>]

>In many cases, though, a token is effectively owned by
>TWO token holders: a hex (or tile) and a company.
>In the real game you then have two physical tokens,
>and perhaps we will show both in our UI, but in the background
>these represent just one property: the fact that one company
>gets a bonus when running through one particular city.

>I think we can best model that by a single object that is owned 
>by two tokenholders, and the token object itself should know both
>of its holders.

This is what I was getting at with my question about non-company related tokens.

If tokens are always attached to a company, then we don't need a new object. We handle all tokens just like we're currently handling Tokens in StockSpace, where the Company holds the token-specific information, and the StockSpace holds a reference to the company.

---Brett.