#2942: ACL model behavior `alias` default value
------------------------------------------+---------------------------------
    Reporter:  nukem                      |         Owner:  Any Developer 
        Type:  Enhancement                |        Status:  closed        
    Priority:  Low                        |     Milestone:  1.2.x.x       
   Component:  ACL (Access Control List)  |       Version:  RC1           
    Severity:  Trivial                    |    Resolution:  wontfix       
    Keywords:                             |   Php_version:  PHP 4 >= 4.3.2
Cake_version:                             |  
------------------------------------------+---------------------------------
Comment (by nate):

 @mhagedon: Going against my normal MO, I'm going to respond to you in
 proper, polite, and relatively lengthy explanatory fashion, in hopes that
 I will be able to refer back to my notes here at a later date, thereby
 saving myself time and effort down the road.
 [[BR]][[BR]]
 First, let me address your point about influence.  While I appreciate your
 interest in CakePHP, and that you hold sway over the opinions of others,
 I'm not going to feel offended if you choose not to use or promote it.  We
 have a vibrant, thriving, and fairly large community of developers who are
 quite happy with it, which thrills me to no end. These people have chosen
 CakePHP because they find it useful and (I hope) enjoyable, however, I
 don't consider it a favor to me that they do so.  I (and others on the
 core team) develop CakePHP in my spare time, at no charge and for no
 compensation.  If you derive some value from our hard work, so much the
 better for you.
 [[BR]][[BR]]
 That's sort of my nice way of saying "don't act like I owe you anything".
 I am under no compulsion to serve your needs, and you do yourself a
 disservice by suffering delusions to the contrary.  That said, I am more
 than happy to listen to any compelling arguments about what we do or don't
 do around here, as far as the code is concerned.  If it works, that's all
 I care about.
 [[BR]][[BR]]
 Good, now that that's out of the way, we can move on to your point about
 my percieved arrogance.  This is a common misconception, given my often-
 abrasive responses, and my generally dismissive attitude towards most
 people.  However, arrogance relates to an exaggerated self-importance,
 which I don't have.  I don't feel that I'm particularly special compared
 to most programmers -- I'm simply impatient.  This is likely a by-product
 my short attention span, combined with the fact that, on most days (today
 included) I have a s**t-ton of work to do.
 [[BR]][[BR]]
 Ergo, I tend to avoid protracted discussions (like this one), and try to
 avoid having to give explanations of why things are a certain way,
 ''especially'' if such explanations can be found elsewhere.  In this case,
 the ACL section of the manual clearly demonstrates two different
 approaches to using ARO/ACO nodes.  In one, nodes are "bound" to a record,
 and have a model name/foreign key that corresponds to that record.  This
 example clearly shows that the 'alias' fields of these records is left
 null.  Likewise, the example that uses aliases clearly shows null values
 in the model name and foreign key fields.
 [[BR]][[BR]]
 As such, one can logically infer that there are two separate and distinct
 ways to reference ACL objects, and further, given that the system provides
 no facility for intermingling the two, that they're not intended to be
 used together in the same ARO/ACO record.
 [[BR]][[BR]]
 This goes to the very core of understanding my response.  No time was
 taken to understand the ''intent'' of the system, or what it was
 ''designed'' to do.  Rather, people simply chose to persistently demand
 the same thing.  As I stated previously, I only care about what works.  If
 you disagree with a design decision, feel free to point out the
 deficiencies and offer a solution, '''but do so from the standpoint of how
 the system under discussion was designed to operate in the first place'''.
 [[BR]][[BR]]
 In summary, I hope this response has been informative and enlightening.
 Have a nice day.
 [[BR]][[BR]]
 - Nate

-- 
Ticket URL: <https://trac.cakephp.org/ticket/2942#comment:10>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

  • Re: [CakePHP : The Rapid... CakePHP : The Rapid Development Framework for PHP
    • Re: [CakePHP : The ... CakePHP : The Rapid Development Framework for PHP

Reply via email to