My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
FAQ  
Common problems and questions
Updated Jan 19, 2011 by kni...@gmail.com

Introduction

This is a listing of common questions and issues, along with their answers and solutions.

Common Questions

Will you ever sell/steal/broadcast/whatever my personal information?

No. App Engine does not even allow access to personal information of user accounts (note: it does allow access to your email address). Any other personal information you upload into the TFX cloud will never ever be broadcast or otherwise given away, unless required by law enforcement or something equally ominous.

Please note that certain anonymous statistics might be collected and broadcast. Things like widget usage statistics and configurations may be shown for the interest of users or be used to provide extra functionality (e.g. widget recommendations) or be used by administrators/developers to track trends.

Will this thing ever be pay-to-use?

The general idea is to keep TFX free. The code is open source, and there are currently no plans to charge for use of the system. However, if it ever gets amazingly popular, there may be some kind of premium features added in order to help defray App Engine costs. If something like that ever does come up, it will be made clear well in advance.

Common Issues

I'm using Chrome and I keep getting prompted by an HTTP login box

This is a problem in the current Chrome stable (version 8). When using SSL encryption (https), Chrome uses an experimental protocol called "SPDY" (pronounced speedy) to speed up the loading process. The current stable version does not seem to be able to use HTTP authentication properly with SPDY. There are two solutions to this:

  • Upgrade to Chrome Beta (version 9).
  • Disable SPDY. This allows you to stay on stable.

This problem is fixed in the beta, and you will also get other upcoming features. However, the beta can be unstable sometimes. I personally have never had any problems, but do so at your own risk.

To disable SPDY in the stable version, Chrome must be launched with the --use-spdy=npn-http option, i.e.:

$ google-chrome --use-spdy=npn-http

Windows and Linux users should be able to add this option to their Chrome shortcut. Mac OS is strange. See here and here for some examples of getting Chrome to work with command-line options on Mac OS.


Sign in to add a comment
Powered by Google Project Hosting