Hi, The general idea seems ok. Are you asking about this because of performance issues or something?
You need to use batch puts / gets where possible. It will help your performance a little bit. Also, I think there is a transactional decorator. You might find it useful to make the code a tiny bit bit cleaner (depending on your preferences). I generally add a "ref_prop_key" @property to my models to avoid the "SomeKind.ref_prop.get_value_for_datastore(item) " stuff being sprinkled all over the place. This also helps reduce the chances of accidental dereferences since I know if I'm getting the key or the entity. Robert On Mon, Jan 30, 2012 at 03:53, HalFas` <[email protected]> wrote: > Hello there, > > I need to design messages system for my users in site. Messages are > 1:1 per pair of members (like sms in iOS), pair of members (2) can > have one conversation which holds all the messages between those > members. > What is the best possible design of such ( in speed 'n' cost ) ? > > Current design looks like this: https://gist.github.com/bcfd2cb0537a432aaa18 > > Looking forward to hear comments, suggestions and possible > improvements. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
