Thanks Sander, 2 could work, but I think I'm left with the same dilemma. Where do I store the data and how do I make it available to the controllers and directives? The goal is to parse the JSON on a per page basis in a few different directives which will build out page specific HTML. The pages are HTML fragments passed in to the $routeProvider. Some kind of app wide cache object that I could pass around would do it.
I haven't been able to find anything directly on point in this forum, or online, so it could be I'm using the wrong terms. Any suggestions there would be helpful. Thanks kindly, stephen On Sunday, January 19, 2014 11:23:04 PM UTC-8, Sander Elias wrote: > > Hi P. > > This is discussed quite a few times already, and there are basically 2 > scenarios. > > 1. Insert the data into the HTML on the server. This is the most used > solution, and you don't need another round trip to fetch the config. If > this is possible for you, this is best way to go. > 2. use a non-angular ajax call, fetch the data, and manually > bootstrap angular after the data comes in. > > There are samples of both already in this group, but if you have further > questions, don't hesitate to ask. > > Regards > Sander > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
