Hi Zack, I could see saving data in the datastore (as a blob, possibly), and retrieving it when needed from there to be a solution.
If I get it correctly, you want to be able to have a single point of access for your object graphs? to me, I'd say the best would be datastore as a blob. Maybe your precise use-case doesn't warrant that though, so if you could expand, it would be great so we can discuss an answer more tailored to your question :) Cheers! On Wednesday, July 1, 2015 at 4:58:25 PM UTC-4, Zak Taccardi wrote: > > I am using dagger for dependency injection, and I don't want to create a > new object graph for every endpoint. > > Android lets us extend `Application`, which is a great place to store our > singletons so they can be easily reused throughout different pages > (actiivities) in the app. > > What is Google App-Engine's equivalent of this? > > > note: I am okay with this being a per-instance thing. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/165b1007-c4f4-4bc1-9069-74c5c2561f2e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
