Yep, i was wrong, i tried creating a calendar entry with a large content size and there were no issues - the API isn't passing data along in the URL at all, it manages to directly POST the contents over. I think i now see how this might be implemented, we can add a hidden IFrame into the page dynamically then build a form inside the frame, also dynamically, and programmatically submit the form, as long as the IFrame contents aren't loaded from a separate domain it can be manipulated like this - by the way, i get a JS "Permission Denied" error in IE6.
Bobby On Apr 6, 9:56 pm, "Eric (Google)" <api.e...@google.com> wrote: > There's not limit that I am aware of. Our XD implementation gets > around this by breaking request/response text into chunks, > and then sending each of these chunks to the browser. > > Eric > > On Apr 6, 10:03 am, Bobby <bobbysoa...@gmail.com> wrote: > > > > > Being able to have a JS client manipulate the GData API fully would be > > a great thing - we would be able to completely detach the apps from > > the server, but i'm 75% confident that there are size limitations to > > this model - this is at least what i have seen when i use JavaScript > > across domains - on my part i'll test this to confirm and post what i > > find here. > > > Bobby > > > On Apr 6, 11:53 am, Kumaravel Kandasami > > > <kumaravel.kandas...@gmail.com> wrote: > > > Thank You Bobby/Eric. > > > > Bobby, we are using js GData Api to remove the server dependency (which I > > > think you are calling the Proxy). Basically the code runs on the client > > > browser and directly does CRUD on GData Service versus request sent to our > > > App Engine Service (python script) and then calling GData Service. > > > > So far, we did not face any issue other than lack of GData API Support for > > > spreadsheets (and documentation), however, we are extending the API for > > > our > > > needs. > > > (Link Eric mentioned in his email - were you could create your own > > > Service - > > > like spreadsheets, doclist, etc). > > > > About uploading content, link below confirms that we do NOT need a > > > physical > > > file inorder to create an new document. > > > >http://groups.google.com/group/Google-Docs-Data-APIs/browse_thread/th... > > > > However, I think we need to spend more time speculating various possible > > > issues with JS API - and post to the group, so it could help us as well as > > > the future developers. > > > > Kumar _/|\_www.saisk.com > > > ku...@saisk.com > > > "making a profound difference with knowledge and creativity..." > > > > On Sun, Apr 5, 2009 at 11:21 PM, Bobby <bobbysoa...@gmail.com> wrote: > > > > > Eric, so the JS library doesn't use JSONP in its implementation? Do > > > > you know if there are limitations to the size of the contents of an > > > > item that can be saved via the JS library? My understanding is (was) > > > > that when making cross-domain JavaScript requests, to get around the > > > > same-origin-policy, you end up having to pass the request data along > > > > in the URL, so you're limited to about 2000 chars or so depending on > > > > the browser. > > > > > Well, anyway, i'll take a look. > > > > > God, i just finished a JavaScript interface to the Python libraries to > > > > act as a proxy, to get around this issue and now i may not need it - > > > > why does that always happen. It's for the best i guess. > > > > > Bobby > > > > > On Apr 5, 7:44 pm, Eric Bidelman <api.e...@google.com> wrote: > > > > > Hi guys, > > > > > The Google Data JS client uses its own XD mechanism to adhere to the > > > > > same-origin policy: > > > >http://code.google.com/apis/gdata/client-js.html#Supported_Environments > > > > > > Although you can use JSONP (we call it json-in-scripthttp:// > > > > code.google.com/apis/gdata/json.html) > > > > > with read-only feeds, the JS library doesn't. Instead, it supports > > > > > the full CRUD model by constructing JS objects. As an example, > > > > > here's > > > > what > > > > > creating data looks like: > > > >http://code.google.com/apis/gdata/client-js.html#Insert_Item > > > > > > Having said all that, the library only supports a few of the APIs: > > > >http://code.google.com/apis/gdata/jsdoc/1.8/index.html > > > > > > Library samples at: > > > >http://code.google.com/apis/gdata/samples.html#JavaScript > > > > > > There's a tip here that may help with the other services: > > > >http://gdatatips.blogspot.com/2008/12/using-javascript-client-library... > > > > > > Hope this helps, > > > > > Eric > > > > > > On Sun, Apr 5, 2009 at 4:11 PM, Bobby <bobbysoa...@gmail.com> wrote: > > > > > > > Good question, i was about to ask something similar. I'm currently > > > > > > creating and updating documents from JavaScript but not directly > > > > > > through the GData Javascript API - instead i exposed a JavaScript > > > > > > interface to the GData Python API on the server-side. > > > > > > > I was just now looking through the GData Javascript API and i saw > > > > > > that > > > > > > you can create calendar entries for instance, but i think there will > > > > > > be significant limitations for creating/updating documents or > > > > > > spreadsheets via the GData JavaScript API. > > > > > > > The reason is that most likely the GData JavaScript API is using a > > > > > > JSONP approach to get around the same origin policy, but this means > > > > > > parameters to the GData functions calls (such as to create and > > > > > > update > > > > > > documents and spreadsheets) will be passed on the URL - so you'd be > > > > > > passing the contents of a possibly large document in the URL - which > > > > > > won't work for large documents and is less than desirable. > > > > > > > If your JavaScript code will be running inside the Google domain > > > > > > (maybe you're doing a widget for iGoogle, or Google Spreadsheets) > > > > > > then > > > > > > you may not need to worry about the same-origin-policy, so you may > > > > > > be > > > > > > able to just make Ajax PUT, POST, DELETE, GET calls directly to the > > > > > > GData API, without limiting yourself by the JSONP implementation of > > > > > > the GData JavaScript libraries (i'm guessing here, if someone can > > > > > > confirm i would appreciate it). > > > > > > > If your code will be running outside the Google domain, then you may > > > > > > have to leave the GData libraries on the server side and expose the > > > > > > necessary functions to JavaScript (in a sort of a proxy setup). > > > > > > > Anyway, i was going to point out that it would be great if there > > > > > > was a > > > > > > GData API Proxy, for example for the AppEngine. > > > > > > > Bobby > > > > > > > On Mar 25, 4:17 pm, kumar <kumaravel.kandas...@gmail.com> wrote: > > > > > > > Hello Team, > > > > > > > > Our intention is to allow user create NEW spreadsheets and update > > > > > > > the > > > > > > > content. > > > > > > > > We are using GData Javascript API and Google Gears, has anyone > > > > > > > successfully uploaded documents using Javascript API into Google > > > > > > > Docs ? Any tips or suggestion ? > > > > > > > > Appreciate your support. > > > > > > > > Kumar- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Data Protocol" group. To post to this group, send email to google-help-dataapi@googlegroups.com To unsubscribe from this group, send email to google-help-dataapi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
