It has no impact on server performance. It just makes the API less clear to anyone who needs to use the CFC: do I need to pass this in or don't I? Setting required="true" when I am actually not required to pass the argument is misleading (in my opinion). I would argue that CF *should* throw an error if I specify an argument as required and then don't pass it in.
On 10/16/07, Aaron Rouse <[EMAIL PROTECTED]> wrote: > > And the downside to the confused API is? These particular CFCs I am > thinking about have been in place for years and heavily used in a shared > hosting environment, the current one being rock steady but I could not speak > for the prior ones since that is before my time. So kind of curious beyond > confusing a person when they look at it, what is the downside in regards to > the server processing it since does not seem to have adverse or must be > minimal effects with the API "confused". > > I actually seem to recall reading a thread about this quite sometime ago > and thought in the discussion people were surprised that it worked one way > vs the other. Maybe was on the BD list because I keep thinking something > specific with that syntax involved BD perhaps it throws an error with BD but > I long since slept since all of that. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
