first on cost. GAE access to cloud storage is free. So you aren't doubling up the cost.
we've done something similar. we store the files in google cloud storage as private objects. We then use GAE to authenticate and deliver the files. I don't know what your idea of large file is, it's been doing ok for us. another way to solve this problem is bypass GAE all together on delivery. You can use the signed url function in cloud storage https://cloud.google.com/storage/docs/access-control#Signed-URLs then you just generate a url in GAE which will expire after certain amount of time. But you deliver the url to the end user. They can download it using their browser within that certain amount of time. On Sun, Jul 26, 2015 at 8:39 AM, Kenchu <[email protected]> wrote: > I'm using Python on GAE, and I want to serve large files to my users. But > only to those who have been authenticated through custom authentication > (i.e. not google). > > The question is how to do this most efficiently. I recon since the > authentication is custom, the request has to go through GAE. I cannot just > use a static file somewhere. So GAE needs to read this file, and send it to > the user. > > The way I've thought of doing it is to upload a file to cloud storage, and > then read it through GAE and send it if the user is authenticated. But I'm > not sure this would be the best way to go about it. Wouldn't this virtually > double the cost? First GAE reads from cloud storage (bandwidth cost), and > then send it to user (bandwidth cost). > > Another concern I have is how long GAE can maintain a connection. These > files are rather big, so sending it could take some time. > > I'm at a bit of a loss here since I haven't done this kind of thing > before. I'm not sure what the best approach is, or if the one I've > suggested is even viable. > > Any guidance or tips would be greatly appreciated. > > Thanks! > > -- > 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 http://groups.google.com/group/google-appengine. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/f18ae707-0dd6-486b-a094-ecac088320d7%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/f18ae707-0dd6-486b-a094-ecac088320d7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Omnem crede diem tibi diluxisse supremum. -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAM0dQnmnXpeBEPC5jp-sgEfFkwCbys-LNGR4tJxdUXtwHmcEqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
