in reply to Re^5: OO Perl Baby Steps
in thread OO Perl Baby Steps

I was merely referring to "locking down" access to certain methods via the concepts (and implementation) of private, protected and public method modifiers. In other words, secure your methods' accessibility from clients.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Replies are listed 'Best First'.
Re^7: OO Perl Baby Steps
by Anneq (Vicar) on Jun 25, 2013 at 10:50 UTC

    Thanks jeffa,

    A lot of my web app methods are activated through URLs, via catalyst, so I want to make sure I'm not missing something I need to know about protecting those methods.

    Anne

Re^7: OO Perl Baby Steps
by Anonymous Monk on Jun 25, 2013 at 03:44 UTC

    In other words, secure your methods' accessibility from clients.

    In other words, deny access, forbid access, put a padlock on it, lock the door, nail the windows shut, eat those pancakes :)

      I do believe Howard Hughes would approve. :)

      jeffa

      L-LL-L--L-LL-L--L-LL-L--
      -R--R-RR-R--R-RR-R--R-RR
      B--B--B--B--B--B--B--B--
      H---H---H---H---H---H---
      (the triplet paradiddle with high-hat)