Yes, I know without huge company name on a front page it sounds scary. But for some small/test apps it can be good enough and really useful. Eventually it will be supported directly by Google, and people will just switch.
I'm using it for a small number of my sites, and with current bandwidth prices there is no reason not to give it away. As some reassurance points I can say: - It is being used for non-Google sites, so this redirector is not going to disappear anytime soon (or when Google will start supporting it directly). - From tech POV it is a lighttpd server without any code at all, redirect is being made at config level. It is not hard to keep that alive. Hope this helps! On Dec 28, 9:22 am, "bruno.braga" <bruno.br...@gmail.com> wrote: > That's a nice workaround for this. > > The only problem here is to convince people to send all traffic to > your IP. > If they need to deal with sensitive data, most likely they will not > turn to this solution. > > On Dec 26, 4:20 pm, Dima U <dimaulu...@gmail.com> wrote: > > > > > Hello! > > > Just a quick note about service that anyone can use to help combat > > "naked" domain trouble. > > > I made wwwizer.com - it redirects requests from naked domains to the > > same with "www." prefix. > > Saving all paths and stuff. > > > Of course it is not as good as having naked-domain support built in, > > but it is better than clicking though domain registrars interfaces. > > > There is no signup or anything "evil". > > > Cheers. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
