On Mar 14, 2014, at 1:30 PM, Chris Raynor <
ch...@firebase.com> wrote:
> Hi Zack,
>
> I'm Chris and I'm one of the engineers building Firebase Hosting. For the initial launch out of beta we're intending Hosting to be for public static assets only, but if we get a lot of interest in access control we'll certainly consider implementing it soon after - I can see it being pretty useful.
>
> Thanks for the feedback
>
> Chris
Cool, ya I kind of assumed that it’s independent for now, so I ended up using the data URI scheme and storing my media files directly in Firebase:
http://stackoverflow.com/questions/13955813/how-can-i-view-and-store-images-in-firebase
http://en.wikipedia.org/wiki/Data_URI_scheme
For now I’m storing the base64 string of the binary data in the database without the “data:image/jpg;base64,” portion, and appending that part with javascript/objective-c before I use it as a URL. My main concern at this point is probably caching, but I’m hopeful that Firebase will replicate that functionality to some degree with its local store. For anyone curious, the transmission overhead of base64 is only 2-3% if the server implements gzip compression in its responses.
In the future, .htaccess support in Firebase Hosting with AuthType or something like it would be cool. Mostly I would like the logic of the "auth != null” lines from Firebase somehow in hosting.
Thanks for the heads up,
Zack Morris