1. Well, I guess that's the best option. Normally from my past experience a "setting file" would include the db connection properties and then I would just add more settings to it.
I guess that as long as I don't need to save settings regarding what to do if the datastore has a problem - it would be just fine Thanks On Tue, Feb 16, 2010 at 11:48 AM, Ian Marshall <ianmarshall...@gmail.com>wrote: > 1. Why not have have a persistent class with one or more instances > persisted to the datastore. You could amend persisted values with the > Administration Console datastore viewer as desired. Your app can look > these settings up as needed. > > 2. Or else construct an administration web page, and allow the > viewing and changing of your app settings from there? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
