| Subject: | Add a cost modelling method to the Target API. |
OK, so it's not what I'm personally going to care about, and probably
not you either.
But you can bet your ass as soon as people start to use for-cost remote
backup systems, they are going to want to know what each backup run will
cost (for the transfer) and how much it will increase their monthly bill
both _by_ and _to_ etc etc.
SO!
You could start by adding an estimated_cost method to the Target API.
This would probably return a hash-ref containing something like (to
start with)...
$cost = {
one_off_cost => 1234, (integer US cents?)
monthly_cost_change => 1234, (could be negative)
monthly_cost_after => 1234,
};
So Filesystem can then be just zero/zero/zero, Amazon (transfer *
0.20)/(change * 0.15)/(after * 0.15), and when GDrive turns up, it will
work too.
Of course longer term those numbers probably need to be a bit more
complex (proper finance shite) but doing it in basic US cents would
probably be enough.
With that working, you could then add a flag that will show the cost
change and then prompt to continue, or something. You know people will
want it :)