As with any platform, experience and knowledge is extremely important and has a huge impact on how long it takes to do things. It can be frustrating to run into issues and stressful if we've promised a deliverable based on a tech stack or service we might not be completely familiar with.
I think it's unfair to be quite so critical given the prompt help that has been provided first for the question about general approach and then for this specific technicality. The docs do mention it and there are a few answers that come up when you search (another one here: http://stackoverflow.com/questions/27281825/google-storage-api-resumable-upload-ajax-cors-error). The solution is very simple so IMO it's no show-stopper. Resumable uploads do have some significant advantages and always seem much simpler than the chunked upload and reassembly that was the previous solution to large file uploading. Just my 0.02c ... On Wednesday, 1 March 2017 01:36:12 UTC-7, Richard Cheesmar wrote: > > Kaan, > > You're spot on regarding impact. You spend most of your time trying to get > over hurdles like these, whilst you should be spending time on the core of > the product functionality. I personally think that the web and the cloud > have become way to complex in this regard and feel it's up to companies > like Google to make functionality like this way simpler. > > I agree that the cloud products such as Googles, especially the app > engine, ndb... have made my project simpler in many ways. However, if what > you gain is then taken away in other ways then you have to consider the > time spent as a whole, not to mention the stress that developers are under > for timelines and costs etc. etc. This particular problem is taking way too > much of my time at the moment. > > > On Monday, February 20, 2017 at 6:47:26 PM UTC+3, Richard Cheesmar wrote: >> >> I am using the standard python app engine environment and currently >> looking at how one goes about uploading multiple large media files to >> Google Cloud Storage (Public Readable) using App Engine or the Client >> directly (preferred). >> >> I currently send a bunch of smaller images (max 20 - between 30 and 100k >> on average), at the same time directly via a POST to the server. These >> images are provided by the client and put in my projects default bucket. I >> handle the requests images using a separate thread and write them one at a >> time to the cloud and then associate them with an ndb object. This is all >> fine and dandy when the images are small and do not cause the request to >> run out of memory or invoke a DeadlineExceededError. >> >> But what is the best approach for large image files of 20mb+ a piece or >> video files of up to 1GB in size? Are there efficient ways to do this from >> the client directly, would this be possible via the Json api ,a resumable >> upload, for example? If so, are there any clear examples of how to do this >> purely in javascript on the client? I have looked at the docs but it's not >> intuitively obvious at least to me. >> >> I have been looking at the possibilities for a day or two but nothing >> hits you with a clear linear description or approach. I notice in the >> Google Docs there is a way using PHP to upload via a POST direct from the >> client... >> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is >> this just relevant to using PHP on app engine or is there an equivalent to >> createUploadUrl >> for python or javascript? >> >> >> Anyway, I'll keep exploring but any pointers would be greatly appreciated. >> >> >> Cheers >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b749ecb8-cc5e-43b5-b506-ec96aa78bafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
