Hi, Simon, Yes, you are correct that some help has been forthcoming. Having said that the help was somewhat disparate in nature. On top of which I have numerous stacks to contend with and can't be king of them all. Still, I thought I managed to find a solution and was content, but alas no, and then there are lots of issues along the way, that need to be resolved. This makes for a very fraught experience for any normal dev. Perhaps I was a little outspoken, a result of hours spent reading online docs that just can't manage to put all the dots together.
Yes, Adam, mentioned that one which I spotted myself last night. And there is the point, you have to hunt all the time and read every single detail or else bam, you get a problem such as this. However, Adam in his initial response mentioned a solution using the Json Api, so I take that as it comes and use it. It works, when you get over the numerous localhost issues, except at the point where it doesn't as documented on the stackoverflow issue. So then you go back to the start and so it goes, more stress and sometimes, it's just enough for you to lose patients! I'll say this as my final 2 cents worth, when you have to continuously use stackoverflow or other such site to find explanations for almost everything, it can be said that this is a partial reflection of the quality of documentation in the first place. Information may be there, somewhere, but is it obvious and clear and for sure as I have mentioned in another post, there needs to be some recipe examples with real code from A to Z so people like me who have to deal with a multitude of code every day can see what is going on. 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/d980324c-42f5-4a90-bb6f-772d7450dc27%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
