It may seem, but it's not trivial at all.
> This seems like a pretty trivial thing to do
The difficulty depends on how 'safe' the solution should be.
I think the logical sequence could be:
1. User asks your appspot for video
2. User is redireced to your video source with an URL get attachment
Hi:
You can write a proxy and this shouldn't be a problem since the data is
binary and you don't need to modify the contents.
Also, large contents may be fragmented, that is, one video saved on more
than one file (Example: file1.rar, file2.rar, ..., fileN.rar). Your
application/proxy may be requir
Hi
I suggest you look at S3, that included facilities for securing files.
T
On Aug 3, 11:04 am, jivany wrote:
> I've been unsuccessfully searching through the group for some pointers
> on how to implement this.
>
> Here's my scenario - I want to be able to push large images and videos
> online
On Aug 3, 12:08 am, Holger wrote:
> The difficulty depends on how 'safe' the solution should be.
Fort Knox of course. ;) No, this is just something to share pics and
vids with the family so it doesn't have to be guaranteed secure. Just
secure enough to keep casual browsers from viewing it all.
To keep browsers from viewing it all you should include the
transmitted video ID into the string (=secret+ID+datetime) which is
MD5 hashed.
> secure enough to keep casual browsers from viewing it all.
Thus an extracted url would be good for an hour of redownload of the
same video but not of anoth
To further expand on what others have suggested, you can implement
this using cookies and authentication similar to what Google Accounts
does for App Engine. The flow would go something like this:
1) Your app generates a token for the currently logged in user,
consisting of their username and the
