Yes, seems like a great idea
Could be called "SimpleVideo"
You would upload a video file, or provide a gcs/aws/cloud source (maybe
even go one step further and provide optional upload urls and libraries for
multi-part uploads, upload continuation in case of disconnects etc. --
blobstore upload
On Fri, Aug 8, 2014 at 10:06 AM, Kaan Soral wrote:
> Thanks Vinny, that is an excellent reply :)
>
> I was trying to get away with a single .mp4 file, but I guess a much much
> complex system is needed for many reasons (other unrelated issues with high
> height videos at firefox etc.)
>
As you
Thanks Vinny, that is an excellent reply :)
I was trying to get away with a single .mp4 file, but I guess a much much
complex system is needed for many reasons (other unrelated issues with high
height videos at firefox etc.)
I guess I should also look into Amazon Elastic Transcoder at this poin
On Wed, Aug 6, 2014 at 12:14 PM, Kaan Soral wrote:
> I'm not acquainted to RTS protocols, it would be great if the answer
> included which protocols are supported in different scenarios
>
> My concern isn't bandwidth but the user experience instead, the videos are
> played only in full screen on
Probably a warm instance, I've checked the logs, no cold instance warnings,
however since warmup requests are enabled, no way to be sure, but since
it's happening always, I'm assuming the instances are warm
The SO question is actually pretty good, but the answer seems dodgy, the
question is abo
On Mon, Aug 4, 2014 at 5:21 PM, Kaan Soral wrote:
> I'm currently using this handler to serve GCS files:
>
> class BlobKeyServeHandler(blobstore_handlers.BlobstoreDownloadHandler):
> def get(self, resource):
> resource = str(urllib.unquote(resource))
> self.send_blob(resource)
I'm currently using this handler to serve GCS files:
class BlobKeyServeHandler(blobstore_handlers.BlobstoreDownloadHandler):
def get(self, resource):
resource = str(urllib.unquote(resource))
self.send_blob(resource)
However there is a very high delay, like 20 seconds, until a
