Looks good to me, but do what works for you and don't try to overengineer for the future. I don't understand why this prevents you from implementing other models.
-- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Oct 28, 2011 at 11:19 AM, Walter Antolini <ant...@gmail.com> wrote: > Hi all, > > I know this topic has already been treated several times, but I must ask > again help to understand how to structure my application: > > My application involves: > 1) frontend > 2) backend > 3) JSON Web API > > Also in the future I will also implement: > > 1) mobile web (for all other mobile phones) > 2) Android / iPhone application > 3) facebook application > > Now I have considered a similar structure: > > app.yaml > application.py > cron.yaml > / app > / config > / controllers > / db > / lib > / models > / static > / images > / scripts > / css > views / > > but with this structure I can not implement other modules. > > What do you propose to me about? > > Thanks in advance. > > -- > 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/-/zrO49_MfGOUJ. > 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. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
