Upload any file type

[GoogleCodeExporter]

Google allow Apps Premier customers to upload files of any type through the 
API. The current version of the gdata API doesn't support this. This ticket is 
to track the popularity of this feature. I'm not a Google Apps Premier 
customer, so I'll be unable to test this feature myself.

Anyway, if this is important to you then comment here. If you want to implement 
it yourself then I'll be happy to help you understand the code and how it would 
be implemented.

Original issue reported on code.google.com by d38dm8nw81k1ng@gmail.com on 17 Aug 2010 at 9:12

[GoogleCodeExporter]

Currently this feature is available for any Google account - you can upload to 
Docs whatever you want.

Original comment by jarek.zg...@gmail.com on 24 Nov 2010 at 2:39

[GoogleCodeExporter]

Whilst this is true for the website, only Apps customers are allowed to use the 
API to upload any file type:

http://code.google.com/apis/documents/docs/3.0/developers_guide_protocol.html#Up
loadingArbitraryFileTypes and 
http://docs.google.com/support/bin/answer.py?hl=en&answer=50092 (at the bottom) 
both explain this. This is presumably to prevent people using Google Docs as a 
free Dropbox/Ubuntu One service.

Original comment by d38dm8nw81k1ng@gmail.com on 24 Nov 2010 at 2:48

[GoogleCodeExporter]

We are interested in using the arbritrary file type upload in our Google Apps 
for Education domains. Can we help to write and test code for you?  Seems like 
it's all in Gnet.upload_file?

Original comment by peter.zi...@gmail.com on 12 Apr 2011 at 4:26

[GoogleCodeExporter]

This should be closable now.

http://googleappsdeveloper.blogspot.com/2011/05/upload-all-file-types-to-any-goo
gle.html
http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=2070

Original comment by gdwar...@gmail.com on 2 May 2011 at 7:19

[GoogleCodeExporter]

I just read that. what you posted gdwar. This is excellent news!

Original comment by polardud...@gmail.com on 9 May 2011 at 6:53

[GoogleCodeExporter]

Does it mean that actual code is ready to upload any file or do we need to wait 
for it to be implemented (from what is written on the blog it seems to be a 
piece of cake).

Original comment by guilo.gu...@gmail.com on 10 May 2011 at 3:32

[GoogleCodeExporter]

Actually, it appears that this is a feature of api v3.  They only have python 
bindings for v2 and honestly, it doesn't look like the maintainers of the 
python bindings are highly motivated to move to v3.  So it may be a while 
before we can use this feature.

Original comment by gdwar...@gmail.com on 10 May 2011 at 3:48

[GoogleCodeExporter]

Is this not the thing one needs?

http://code.google.com/intl/ru-RU/apis/documents/docs/3.0/developers_guide_pytho
n.html

Original comment by i...@ivlis.com on 11 May 2011 at 8:12

[GoogleCodeExporter]

I believe v2 of the Python library supports the v3 GData API, they just use 
different numbers.

Original comment by d38dm8nw81k1ng@gmail.com on 11 May 2011 at 8:35

[GoogleCodeExporter]

Yes. Could be true.  Maybe I got caught up on the v2 of the library and you're 
right that they're not the same.  So here's the question: Have you been able to 
upload anything?  I've only tried with the 'googlecl' tool and it failed.  

Original comment by gdwar...@gmail.com on 11 May 2011 at 7:35

[GoogleCodeExporter]

I reviewed "Google Documents List Data API v3.0" in Labs, I found the reading 
somewhat ambiguous. Does the latest API support uploading of any file types?
Is google-docs-fs going to support this feature when it is out of the "labs"?

Original comment by mark.la...@googlemail.com on 29 May 2011 at 5:39

[GoogleCodeExporter]

So any idea on when we will be able to upload any file?

Original comment by polardud...@gmail.com on 24 Jun 2011 at 4:22

[GoogleCodeExporter]

Is this still being updated?

Original comment by polardud...@gmail.com on 20 Sep 2011 at 6:21

[GoogleCodeExporter]

I'd like to change the code myself to support any filetype.
How can I change the source so that it can be integrated in the main stream?
Any hints in how do "not mess up" the code?

Thanks

Original comment by jones12...@gmail.com on 19 Nov 2011 at 3:38

[GoogleCodeExporter]

#14: I believe the best way to do it would be to make your modifications, test 
them, then create a diff patch and attach it here. That would probably be the 
best way to get the source integrated in the main stream. As for not messing up 
the code, As long as you know what your doing, you shouldn't be able to mess it 
up too bad. :D

Original comment by dreamcas...@gmail.com on 20 Nov 2011 at 6:23

[GoogleCodeExporter]

Thanks! I'll start it in a week or two and post the progress here. I just hope 
no one is doing it already, so I don't work in vain :-)
Best regards

Original comment by jones12...@gmail.com on 21 Nov 2011 at 3:09

[GoogleCodeExporter]

Sounds great, can't wait to use your patch, currently the only reason I haven't 
started using this yet is this issue.

Original comment by dreamcas...@gmail.com on 21 Nov 2011 at 3:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi, I got an alert that someone had commented but it seems to be here no longer.

I would recommend that anyone wishing to resolve this issue fork this project 
on Github or Bitbucket and send me an email.

I'll happily link the project on the home page to send traffic your way.

Regards,

Scott W

Original comment by d38dm8nw81k1ng@gmail.com on 18 Apr 2012 at 8:14