getDataFeed should return feed

[GoogleCodeExporter]

--------------------------------------------------------------------------
NOTE: This issue tracking system is for developer products only.  If you
are not a developer/programmer and have a problem with a Google web site,
please report the problem to the appropriate group.  More information can
be found here: http://www.google.com/support/
--------------------------------------------------------------------------

Name of API affected:
Analytics Data Export API

Request summary:
Provide a brief summary of the the feature you'd like to see implemented.
Would like to see the getDataFeed method return the feed itself instead of
sending it straight to the continuation function. This would allow for a
re-utilization of code when multiple URI feeds are being used (multiple
requests with differing date ranges) and additional parameters could be
passed to the processing function instead of only the feed object.

Use Cases:
Describe how you will use this feature if implemented.
This would allow me to use the same function to process similar data that
only varied in date range and to send to that function the id of the div to
write the data to. Using this method I slim down my code while allowing the
end user to compare data from multiple date ranges.

Original issue reported on code.google.com by christop...@gmail.com on 12 Oct 2009 at 7:18

[GoogleCodeExporter]

Hi,

This was a design decision made by the Google Data JavaScript Library which 
analytics uses to surface it's data. The main reason for a continuation 
function is that 
JavaScript is single threaded, meaning the entire browser (or tab depending on 
browser) will wait until the function returns. Because this is a client/server 
request 
which could take a couple of seconds, the user would be stuck with a non-
responsive browser until the function returned.

The continuation function allows the request to happen asyndhronsouly, and not 
have the user wait for the function to return.

If you're looking to pass additional parameters, you could create an object 
with the 
parameter data, and use a method of the object as the continuation function. 
This is 
what was done on the query explorer, which you can look at for more details.

For more discussion, please use our public google group.

Thanks!

Original comment by nickski1...@gmail.com on 30 Dec 2009 at 9:59

• Changed state: WontFix

[GoogleCodeExporter]

Removing an obsolete label that was used when these issues were in the 
gdata-issues project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:04

• Removed labels: API-Analytics

[GoogleCodeExporter]

Changing the issue type to match the organization desired in this project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:06

• Added labels: Type-Feature