I agree I actually think a Expando model might be more appropriate combined with adapters.
That way you can store additional information if required due to different requirements, but keep the specific state based methods in the adapters, if you don't want to start aggregating methods from different states. However I would seriously look at your models to see if you not in a situation where you have a "pattern" you want to use, which doesn't really suit the environment in which your developing. Often patterns described suit the restrictions of specific languages like Java, and python has it's own approaches. See ya Tim -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/miS3BJices4J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
