Nathan, I too like the idea of having a tidy way to serialize objects, for this reason alone, its worth having an additional layer. I've been using the scope "my" however. ;) Btw, what is the difference putting the
<cfset instance = StructNew() /> in the psuedo-constructor vs a normal constructor? I do the latter.. // John, personally, I don't think cfinclude and cfc's should be in the same sentence. :) The whole thing reaks of breaking encapsulation.. // Stace, there's nothing wrong w/ "this" anymore. You can't serialize "this" into wddx (yet) tho and that's the big bonus of storing your fields (properties) in a struct. Also hides things a little better.. Although being able to say session.user.username is less keystrokes than session.user.getUsername() // I suppose overall maybe a rule of thumb might be, When planning to serialize or create mulitple instances of a CFC use a protected scope such as 'instance' (or 'my')-- when designed as a singleton don't bother? ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
