Curtis Olson wrote:

> Definitely nice work on the page layout.  It's my job to play devil's
> advocate so to speak, [...]

My concerns are of similar nature, and locking the project into
Google's infrastructure without any option to pull out doesn't sound
intriguingly. But since I knew that you'd play the role, I was happily
taking the easy route  :-)

> - We would be forced to host the site on google's servers (free hosting up
> to a certain bandwidth/cpu limitation)

Recent history has shown that there's no drawback compared to the
current solution.

> - There would be no possibility of ever moving/porting the site to another
> host because the entire site is dependent on the google apps infrastructure.

I don't think so - well, depends on which parts of the framework are
being used. According to this document:

  http://code.google.com/intl/en-intl/appengine/docs/python/overview.html

.... there's always the option to use the Django framework and from a
quick glance I'd say that even the Google Python datastore API seems to
be very similar to the Django database API. Therefore I suspect that
such a site would be pretty portable as long as no "webapp"-framework
specific code is being used and I also don't see a reason why the
Google datastore content can't be written into some (portable) dump
file.

Cheers,
        Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

------------------------------------------------------------------------------
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

Reply via email to