CDK should support newly added `controller_size` and `controller_copy`

[enzoh]

[enzoh]

This is especially necessary due to #15

[enzoh]

Owing to the fact that the canister's initializer, used for access control, does not persist across upgrades.

[hansl]

These are not in the public spec yet (they're internal APIs likely to change), so I'll mark this as blocked.

[levifeldman]

This is a helpful feature, can a canister see the list of its own controllers? many canisters will want to limit some methods for their controllers.

[nomeata]

many canisters will want to limit some methods for their controllers.

The recommendation is to not conflate canister controller with application level roles, and implement your authentication logic in the canister as you see fit, for example using an admin list. You can initialize it with the controller upon installation.

Or would you expect that on a LAMP system, the system's root user can log into the web application running on it?

[levifeldman]

That may be for the old model of the web, where users never own their data. I want my users to controll their own canisters, so that they controll and own their own data in the truest way. The controllers are the admins and the admins are the controllers.

[levifeldman]

Oh I can call the management canister canister_status.

edit- better if I can get the controllers in a synchronous way and without keeping the canister as its own controller.