Martin Spott wrote: > Pete Morgan wrote: > > >> A Major issues is that GAE does not support binary files very well, eg >> gallery, so I'm not sure how this would work. One possibility would be >> to rename the current machine as "www2." or "stash." and using it as the >> binary storage. >> > > To my understanding, one of the issues with the current web service is > the transfer volume limitation. Thus, if you/we use this as a dump > store, we don't gain much. > As an alternative, storing the bare imagery elsewhere, on a separate > SVN repo or the like could be an option. > bin.go! (oohh no.. go is a google language as well....)
At least with svn there are a lot of committers that can be "censored.. oops vetoed". There is a huge issue of "vetoing" uploaded images for example, or pointers to other sites. This way many comitters can be tracked, promoted and maybe banned as required, before it gets into trunk. This would remove some of the maintenance issue also from www.flightgear.org as well as the bandwidth. pete >> Maybe we should ask Google to sponsor FlightGear? >> > > They already 'sponsor' the project in some way - don't they ;-) > > Cheers, > Martin. > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
