Search results for "dist:Entities feature"
Entities::Feature - A certain functionality, or just plan feature, that customers can use.
A feature is just a name for some functionality or feature in your webapp, that you want to limit the availability of to certain privileged customers only. A feature is the basis of feature-based authorization. NOTE: you are not meant to create featu...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities - User management and authorization for web applications and subscription-based services.
Entities is a complete system of user management and authorization for web applications and subscription-based web services, implementing what I call 'ability-based authorization', as defined by Abilities and Abilities::Features. This is a reference ...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Plan - A collection of features (possibly scoped and limited) customers can subscribe to.
A plan is merely a collection of features. Customer get access to these features by subscribing to a plan. In a paid webapp, for example, you might have plans such as 'Free', 'Small', 'Medium' and 'Large', with feature count increasing from plan to p...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Role - A collection of possibly related actions granted to users.
A role is merely a collection of actions. Users are assigned to these roles to easily provide them with abilities they might need, probably to perform their 'roles' in a webapp (think of roles such as 'admins', 'members', 'vandal_fighters' or 'trolls...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::User - A user entity that interacts with a web application.
A user is an entity that interacts with your webapp. Generally, this is a human person that has signed up for your service, or was created by a customer, though it could be a privileged bot or whatever. The user is that actual entity the performs act...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Action - A piece of code/functionality that a user entity can perform.
An action is just a name for a piece of code or some functionality in your code, that you want to limit the availability of to certain privileged users only. An action is the basis of ability-based authorization. NOTE: you are not meant to create act...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Backend - A role providing storage for the Entities user-management/authorization system.
This class defines a Moose role that is to be consumed by backend classes that provide storage for the Entities user management and authorization systems. It defines a list of required methods that every class that consumes this role must implement....
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Customer - An abstract entity that owns users and subscribes to plans.
A customer is a company, organization or individual that have subscribed to use the services of your ability-based webapp, possibly paying for it. This customer entity can subscribe to different <plans|Entities::Plan> and use the <features|Entities::...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Backend::Memory - A simple backend that stores all data in memory, for testing and development purposes.
This backend for the Entities user management and authorization system stores all entities and relations between them in memory. It is only meant for quick testing and rapid development. Please, do not use this in production environments....
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC
Entities::Backend::MongoDB - Stores all Entities data in a MongoDB database.
This backend for the Entities user management and authorization system stores all entities and relations between them in a MongoDB database, using the MongoDB module. This is a powerful, fast backend that gives you all the features of MongoDB. This i...
IDOPEREL/Entities-0.5 - 04 May 2013 13:30:43 UTC