renewing/subscriptions

[kristopolous]

this is harder than it appears. the system needs to be smart enough to account for gaps in duration AND smart enough to pack all the times it was live into one view.

So yes, you could have the accounting in some separate one-to-many table blah blah blah, ok sure.

you could also have some ref_id system and use actual separate campaigns and then just hide this abstraction from the user, ok sure.

But these are both kinda lame so I'm punting this hoping that some great third option will come along that doesn't sound so wacky.

[kristopolous]

The first solution allows us to build campaigns and not set them "live" and to key purchase ids not to campaigns but to actual commitments to play.

[kristopolous]

if they're viewed as "contracts" I'm ok with it. The user purchases a new contract on a campaign. Then we have to decide whether we want to be pointing to contracts or campaigns.