google-drive-realtime-api

I have an iframe with a published Google Doc. The contents of that doc are subject to change, so I want to auto adjust the height of the iframe based on its content. I found some solutions for this, but they all require access to the head of the child document. Does anyone have an idea on how to do this? You can view an excerpt of the code I use below: #faq{ height: 800px; overflow: hidden; position: relative; width: 660px; border-top: 1px solid #90C547; border-bottom: 1px solid #90C547; } <div id="faq"><iframe id="faqif" src="https://docs.google.com/document/..../pub?embedded=true"

I have tried to get an access token using the REST API by passing the parameters which are shown in screenshots below, but I face the error Required parameter is missing: grant_type . I have tried with cURL and the Advanced Rest API in a Chrome browser. I am sending these parameters using cURL and the Advanced REST API: client_secret;xxx refresh_token; redirect_uri;https%3A%2F%2Fwww%2Eexample%2Ecom%2Foauth2callback scope;https://www.googleapis.com/auth/drive client_id;xxxxxxxx.apps.googleusercontent.com access_token; cURL syntax: D:\>curl -k --header Content-Type=application/x-www-form

I am trying to understand how the Realtime API Resource Model is "shaped", in order to work with ' get ' and ' update ' features. Unfortunately documentation doesn't not say nothing about it ( https://developers.google.com/drive/v2/reference/realtime#resource ). I went to try by myself using the ' get ' request provided in the docs ( https://developers.google.com/drive/v2/reference/realtime/get#try-it ), so I created a new one realtime doc (using the Google Drive Realtime API Playground) and I passed the fileId to the ' get ' request. What I am getting back, in the response body, is a base64

For months I've been using the Google Drive API for simple access to fetch metadata about publicly shared document IDs. All of a sudden about a week ago (April 16) it stopped working. I've tried repeatedly from different machines (PCs and Linux servers) with browsers and cURL and WGET, and I have even created new Google API accounts to try using different API keys, but it fails 100% of the time. Example request URL: https://www.googleapis.com/drive/v2/files/0By7D4SJX3kYEaGpneE1VaUN6OG8?key=MYAPIKEY Response body: { "error": { "code": 500, "message": null } } Response headers: HTTP/1.1 500

Over the last couple days I've been seeing some increasingly problematic issues with a long running realtime app. I've walked through the steps below and the code snippet at the bottom contains additional debug info from the app. When the page first opens it successfully requests an OAuth token and loads the realtime doc [A]. After 50 minutes (10 minutes before the token expires) it re-requests a new OAuth token successfully [B]. After the first token has expired the currently open connection gets a 401 unauthorized error and requires a new oauth token [C]. This in itself seems like a problem