Defining application models with Cream

[Kenny Meyer]

Hi all,

in my web application I will need these user types: Contestant, Judge, Administrator.

What is the best way to represent them in a model or models in Cream?

Should I create a model for each user type, or is it enough to create a single User model and manage them with roles?

[Kristian Mandrup]

It all depends on your requirements. The User Types should be
considered User Accounts. If you have a case where you have different
system requirements for each type of user, such as different data,
registration flow, registration page or similar, then have multiple
accounts. For simpler cases you can handle it with roles.

I am working with @stanislaw on a new project called "tango" which is
meant as a replacement for Cream. I also have a project called
"troles" in the works, which is a new and better roles solution.

Kristian

[Kenny Meyer]

> It all depends on your requirements. The User Types should be
> considered User Accounts. If you have a case where you have different
> system requirements for each type of user, such as different data,
> registration flow, registration page or similar, then have multiple
> accounts. For simpler cases you can handle it with roles.

I figured out, that my application didn't require so fine-grained
authorization as in Cream, so I just went with CanCan after digging
into it.

> I am working with @stanislaw on a new project called "tango" which is
> meant as a replacement for Cream. I also have a project called
> "troles" in the works, which is a new and better roles solution

Troles really looks much better and easier to use. You should make a
big fat disclaimer on the GitHub project index referring to that
project.

Thanks a lot for your answer.

Kenny