Guys, What about using cfproperty for this?
On Nov 6, 3:30 am, Bassil Karam <[email protected]> wrote: > I think the need will quickly arise to be able to choose which properties of > a cfc to store in google. A designated scope, like "variables.instance" or > "variables.i", where you could put properties that you want stored in > google, could be a good idea. > > Baz > > On Thu, Nov 5, 2009 at 3:35 PM, Bassil Karam <[email protected]> wrote: > > Or maybe this would be better: > > > MyNewCFCInstance = > > ColdspringWiresUpComplexDependenciesForExample.getBean('MyCFC'); > > MyNewCFCInstance.googleRead('Key'); > > > ? > > > Baz > > > On Thu, Nov 5, 2009 at 3:27 PM, Bassil Karam <[email protected]> wrote: > > >> So if the CFC had a dependency to another CFC (that is NOT persisted like > >> AppConfig or Validator), will the CFC be created without error, but it is > >> up > >> to me to populate all the dependencies once I get it back before I use it? > >> For example: > > >> AppConfig = createObject('AppConfig'); > >> MyCFC = createObject('MyCFC').init(AppConfig); > >> MyCFC.setDate(now()); > >> MyCFC.googleWrite('MyCFCKind', 'MyKeyName'); > > >> Now to get it back: > > >> MyNewCFC = googleRead('MyKeyName'); > > >> But this won't be functional because it depends on AppConfig, so I have to > >> then do: > > >> MyNewCFC.setAppConfig(AppConfig); > > >> And now I would be back where I started, right? And it won't error out in > >> between, right? > > >> Thanks for answering all these questions! > > >> Baz > > >> On Thu, Nov 5, 2009 at 3:16 PM, Vince Bonfanti <[email protected]>wrote: > > >>> Currently, you'll have to persist the two CFCs separately. > > >>> Vince > > >>> On Thu, Nov 5, 2009 at 6:04 PM, Bassil Karam <[email protected]> wrote: > >>> > Oh nice. How do you handle CFC dependencies to other CFC's? What > >>> happens if > >>> > another CFC is stored in the variables scope, is that then serialized > >>> or is > >>> > the process recursive? > >>> > Baz > > >>> > On Thu, Nov 5, 2009 at 2:57 PM, Vince Bonfanti <[email protected]> > >>> wrote: > > >>> >> No, we're not serializing CFC's anymore, so there shouldn't be a > >>> >> problem with versioning. Basically, the CFC "variables" scope is > >>> >> persisted to the datastore; when the CFC is retrieved from the > >>> >> datastore, a new instance is constructed and the "variables" scope > >>> >> initialized with the persisted values. > > >>> >> Our plans are to implement syntax that's compatible with the CF9 ORM > >>> >> feature for persisting CFCs, in which case the current syntax for > >>> >> persisting CFCs may be deprecated. > > >>> >> Vince > > >>> >> On Thu, Nov 5, 2009 at 2:36 PM, Bassil Karam <[email protected]> > >>> wrote: > >>> >> > I noticed the datastore can still store and save CFC's (as well as > >>> >> > structs, > >>> >> > which is awesome) does that mean they are still being serialized and > >>> if > >>> >> > their signature changes there will be errors? > >>> >> > Cheers, > >>> >> > Baz > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
