Uses cases of this module.

Hi all, for a quick understanding of the module scope It would be interesting to know the use cases (within the drupal context) the module should provide functionality, ..

- http://drupal.org/node/86245 - How to create content AND register a user at the same time
Should a user visiting a page, be able to create content and this content be assigned to a temporary user for later management.

For this I've found a case (quite used in internet) currently can't be achieved in drupal: You can create a product for selling (using your email address while you submit the content). The selling post remains hidden (unpublished in this case) untill you confirm an email. The confirmation is just a link you can use several times to 'login' and edit and post attributes, for example, the published status. The account and the post will be deleted after a period of time (even if active). Each post submission gets an account, because the login "link" grants permissions for a post: one post -> one user. (This can be easily extended so all posts of the same email address go to the same account, but in this case the deletion is not so clear).

- Navigate the site as if he did register, as a test user
Should a user visiting a page, be able to have more permissions than anonymous user.

I certainly understand this as completely temporary users, to be able to test a site feature. Optionally they can configure the account to keep it. The "Test site" link can provide the account and login the user.

- Navigate the site, providing an account that could be configured later
Should a user get an account breaking completely the registration process

This one I've found quite complicate, because of the lack of requirements for a lifetime account (profile required fields, other module's requirements). Optionally the account will be abandoned so it can be deleted.. How and when a users decides to participate in the site, so there's the need of create an account? casting a vote? creating a node? making a request? these three cases could be achieved in the first case: create content while registering..

I can't see where is the need of handle the 403 error in any of this cases. Am I missing something? Which of the previous cases is the most important? what are other cases I'm not considering?