We'll have to see how people actually use this in practice. Our thinking was that you will normally not want to specify a keyName, but will prefer to use the automatically-generated key. However, it may be desirable to specify the "kind" in order to be able to search collections of heterogeneous CFC types (remember, a "kind" can consist of objects of different types, so I could have a "People" kind that contains CFCs of type "User", "Customer", "Vendor", "Student, "Teacher", etc. and then search the "People" kind to retrieve multiple different types).
Vince On Mon, Nov 16, 2009 at 2:55 PM, Bassil Karam <[email protected]> wrote: > My pleasure :) > > One suggestion I would make to Vince is to reverse the positions of the > attributes "kind" and "keyName" and to not make "kind" required if "keyName" > is specified. For example, if I wanted to save an object, I could do: > > googleWrite(MyObj); > > This will automatically populate the kind and the keyName, but if I had my > own key name, it seems I should be able to simply provide it: > > googleWrite(MyObj, 'MyKeyName'); > > With the "kind" automatically populated as before. Why should I have to now > specify it just because I have a key? > > Similarly if you invoke googleWrite on the component itself: > > MyObj.googleWrite('MyKeyName') > > I think keyname is going to be specified MUCH more often than kind and > should therefore precede kind in the attribute list and also not be tied to > it. > > Just some thoughts, > Baz > > -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
