Thanks for the reply. My data would be coming from the server which holds a MySQL database. So in the scenario I outline, the batch job would read the most recent 6 or so datasets frpom the database, and then create images or static instruction files (which would be included in the homepage to make requests to Google). The images / charts would then be displayed in the homepage to show the most recent visualisations. Clicking on an image or button would take the user to a page showing the full visualsiation along with data.
On Aug 16, 10:46 am, Joseph Moosman <[email protected]> wrote: > How is your data being supplied to the app? > > I'm thinking I would approach this problem on the server from the data side. > I'd probably use PHP. > > I would save data sets every hour (as queries or views, for example) , > create URLs to the queries in PHP and let users bring them into the app on > demand in a browser. > > This would have several advantages. You wouldn't have to tear up the api > itself - in fact you would do nothing to the api - and the resulting > "snapshots" would be fully dynamic visualizations. Not dead jpg files. > > Just my 2 cents. > > Hope this helps. > > On Mon, Aug 16, 2010 at 11:36, Mr Morgan <[email protected]> wrote: > > Or can somebody suggest another alternative? > > -- > Vänliga hälsningar, > > <http://www.alati.se> -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
