Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re: managing object permissions

by Bloodnok (Vicar)
on Nov 26, 2008 at 17:18 UTC ( #726158=note: print w/replies, xml ) Need Help??

in reply to managing object permissions

LDAP (Lightweight Directory Access Protocol) is a means by which a TCP/IP based database(s) are accessed.

.oO(I'm sure I'm teaching my granny to suck eggs, but here goes anyway...)

As far as hierarchy is concerned, why not fall back on the inheritance of methods, accessors & mutators e.g. in your example, Desk->method() resulting in Workflow->method() actually being the method called - thus indirectly implementaing the inheritance of permissions etc. e.g.

package Workflow; sub method { my $self = shift; . . . } package Desk; use base qw/Workflow/; sub new { bless \( my $scalar ), ref $_[0] || $_[0] } package main; my $desk = Desk->new(); $desk->method();
etc. etc.

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: managing object permissions
by LanX (Bishop) on Nov 26, 2008 at 17:36 UTC
    I think another kind of inheritance is meant.

    Perls OOP models inheritance on classes not on objects. Objects have no @ISA.

    IMHO the OT has objects of different classes in a hierarchical order

    but he may simulate the @ISA behaviour für objects in an instancevariable @upper_rights containing refs to the other objects.

    Cheers Rolf

      Agreed - but I've played with inheritance at both class and instance level in order to achieve substantially the same, or similar, end-result.

      A user level that continues to overstate my experience :-))

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://726158]
[Tux]: Discipulus thanks. That is an **old** post (from Juerd, whom I know personally). I'll check it out

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (10)
As of 2018-05-24 08:15 GMT
Find Nodes?
    Voting Booth?