One simple but less-than-ideal solution is to setup a light weight reverse http proxy on a server that has a non-blacklisted ip, but has no restrictions when connecting to GAE. This would definately work, but there are two major disadvantages:
1. You pay for the 3x the bandwidth. Going into the reverse proxy, going out, and again into GAE. 2. Additional latency/less scalability. On Dec 2, 9:37 pm, DBPZ <[email protected]> wrote: > Hi guys, > > The google appeng really gives me so much fun and the free quota is > very delicious such that some REAL applications may be run within it. > However, when I considered to do something big here, I found a problem > that I cannot apply for a dedicated IP address for my applications, > while most users of my potential applications are from an Asia > country. Any attempt of deploying my applications behind an IP address > that is shared with some other unknown users may results in being > blocked at the network borders because of some offensive to policies > of that country. If it happens, I even cannot save my applications by > moving it to another provider because nowhere else provides the same > sandbox. > > Not only to me, this issue may draw back other serious users > (especially businesses, which are more valuable to Google) considering > the global accessibility of their applications. I wanna know if there > are some solutions to this concern, for example, allowing users to > choose their deployment points (for example, in the target country of > the application) or building some tunnels across the network borders > being supervised by authorities. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
