Sorry, you're right. I was thinking about how you get the datatable /for/ a visualization, which is defined to use GET.
So yes, a visualization could use any method to send its data to a server (or indeed no method at all, since a lot of them dont require a server). So POST is probably the way to go. Mark On Dec 16, 4:46 pm, codingGirl <[email protected]> wrote: > I am not sure I am following you. Google Visualization World doesn't > promise anything about how the data is sent if I am not mistaken. > > Also Google Chart and Google Visualization are two different animals. > In fact Google Visualization is using Google Chart for the Image > Charts which are overcoming the 2000k limit - meaning they do not use > GET to send their data. > > I wonder what they use? > > On Dec 16, 5:28 pm, Markw65 <[email protected]> wrote: > > > > > Well, actually, encoding the data in the url is /exactly/ how the > > image charts work. > > > And yes, it does mean that the url length is limited - eg ie6 limits > > it to 2k on the client side. Also, some servers will limit it > > (although I dont think google's chart servers do that). > > > If you want/need to get around that, you can use "POST" instead of > > "GET" with an XMLHttpRequest from javascript. Then you can send > > whatever (and however much) data you want. > > > But then you're outside of the google visualization world, and are > > working with your own protocol. > > > Mark > > > On Dec 16, 7:51 am, codingGirl <[email protected]> wrote: > > > > Nobody can at least give a hint how to do this? -- 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.
