[google-appengine] Re: Google has fixed 30 of 707 bugs reported in the past 12 months
That's too bad Google is not improving GAE as much anymore. We (company) are now using Spring/Tomcat AWS and Postgres because it's more up to date (Java 8), flexible and AWS has great (paying) support. GAE is a great platform though, beats them all IMO but it needs some improvements like Java 8, ORM, emails (that was removed), etc.. GAE is definitively a gem. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/410f374b-a26f-4431-a19c-934144c1f531%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] All datastore calls failing
works for me. On Mon, Apr 9, 2012 at 7:16 AM, Ernesto Oltra ernestoka...@gmail.com wrote: Hi, Since 30 minutes more or less *all* my datastore calls (get, update put, query) are failing with either of this two: API error 5 (datastore_v3: TIMEOUT) Canceled: Deadline exceeded I've tried updating a new version and shutdown the instance, but no result; all calls (even a simple get by key!) fails. The appid is historypoint-hr. Ernesto -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Bq6zttUNtqgJ. To post to this group, send email to google-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Downtime
I feel your pain. Am I the only who is extremely shocked to find out that once your daily quota has been exceeded you should brace yourself for hours of downtime because billing is not automated ? It's very disappointing. GAE is good at automating suspending websites, but fails to automate billing? -- 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-appengine@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.
Re: [google-appengine] Re: fetching by keys (as strings) is kind of slow
There is no way fetching a key takes 3 sec. There is a problem either on your side or on GAE's. -- 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-appengine@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.
Re: [google-appengine] Re: Google App Engine community support is moving to Stack Overflow
“Well, over all I think the most of the community is behind it, but Supercobra, and Brandon, the guy in the mermaid costume, have expressed some concerns” “Really? Did you ask G.I. Joe and Batman what they think?“ supercobra's opinion is more important than batman's, because batman can't code all that well anyway -- 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-appengine@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.
[google-appengine] Re: Google App Engine community support is moving to Stack Overflow
I think this is a terrible idea because it makes people check 2 places and subscribe to 2 boards. Newcomers to this discussion will have a hard time knowing about this. App Engine team does put enough resources for community and customer support. I have a paid app and I cannot get my simple billing questions answered. In the billing interface, there is no link or phone # to use. Just a link to this forum... unless we pay become a Premier Account for $500 / month but first we need to talk to the sales team. Really? So desperate users in need of urgent help post questions on forums and if they make enough noise and show enough distress, others users help them and sometimes, in with their immense goodwill and too little available time, Google Engineers help too. Google App Engine team says, 'well support is best effort around here or get a Premier Account'. I think this is not the way to do it. Together with Google engineers, WE make Google products what they are because of our deep involvement. This lack of support is general across most Google products. Our company uses many Google products that are now business critical for us: Google Apps for Business, Checkout, Analytics, and more. With all of those, if you have a problem, well, it's your problem because you cannot contact anyone. So is it hard to provide good support? Not for every company. We use Amazon S3 and Cloud Service. We are a little tiny customers for them. The other day we had a problem that brought down our SaaS app. Emergency. What do you do when that happens? Well, simple. On Amazon AWS console, click on 'call me I need help now' button and a human calls you within a minute. So Google: use a tiny portion of the immense net revenue to add more community and product support engineers. I bet that will improve the bottom line even further. One last BIG concern. One of the things that first get dropped when a product is going to be retired (i.e. killed) is developer and community support. Java and Python appengine discussion groups are being deprecated and dev support is moved to Stack Overflow. That does not sound like App Engine is going forward to me. More like a huge red flag. Is App Engine business in danger? Telling Google users to use Stack Overflow is the equivalent of displaying a big sign on Google Groups home page saying use Stack Overflow, it's much better than what we have. As other users suggested, Google should improve this forum software and make it work more like Stack Overflow and not move there... -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/-CMqxkvEya4J. To post to this group, send email to google-appengine@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.
[google-appengine] Storage stats discrepancy in usage stats v.s.billing
Hi Google, When I look at my app stats 'Datastore Statistics' I see - Size of all entities = 979 MBytes But in the billing history page I see: Datastore Storage $0.008/GByte-day used: 5.50 free: 5.50 Billable 5.50 Charge: $0.04 So one says I am using about 1GB the other one about 5GB right? Is there a discrepancy or just something that escapes me? app_id=playtyprx URL: http://app.typrx.com Thank you. Daniel -- 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-appengine@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.
[google-appengine] Suggestions needed to implement REST for our Java App Engine back-end
Hi there, I'd like to get some framework / library suggestions to implement a REST interface to our Java App Engine back-end. We are looking for a lightweight solution if possible. Thank you. Daniel -- 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-appengine@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.
Re: [google-appengine] Least Expensive Way to Delete Entities
Could you explain (again?) how a deletion of an entity w/ 10- property is 21 writes? On Mon, Dec 19, 2011 at 3:18 PM, Ikai Lan (Google) ika...@google.comwrote: One thing you can do is making this really slow. The free quota actually gives you quite a bit of quota (if your app is relatively small) so if you can stretch out your job you can purge a relatively small datastore at low cost. I suspect what makes this expensive is datastore ops, not instance hours. Deleting an entity with 10 properties is 21 writes! There's not a lot we can do there ... -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Mon, Dec 19, 2011 at 9:50 AM, Patrick Twohig patr...@namazustudios.com wrote: Hi, I have a bit of old data that I want to clean out. I tried to write a fanout operation to clean out some of the old data, but it's actually manged to run out my budget in a few hours. I'm curious if there would be a way to delete huge amounts of old data that isn't needed anymore. Is there a tool or something that i can use to efficiently purge entity groups from my application? Any help would be greatly appreciated. Thanks, Patrick. -- Patrick H. Twohig. Namazu Studios P.O. Box 34161 San Diego, CA 92163-4161 -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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.
[google-appengine] www.TyprX.com typing app 100x more expensive under new pricing
Hello there, Our typing race game www.typrx.com will be 100 times more expensive (w/ the 50% discount on the front end till end of Nov.) under the new pricing. This places us in a difficult position because we need to allocate resources *now* to work on this, and we are already very busy We have not optimized it yet, however, it is already using all the good stuff like Memcache... and even if we shave 20% of resource usage this is still very expensive. As TyprX becomes more popular, we won't be able to afford its cost and would either have to move it to another platform (and rewrite the backend) or stop it altogether. I am not too sure what we should do at this point. Google App Engine: please help. -- Daniel www.metadot.com -- 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-appengine@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.
Re: [google-appengine] Want to talk to the App Engine team in person?
Hi Greg, ... I'm curious to know which prices you are comparing App Engine's new prices to when you say it is priced out of the market. All of the comparisons we've done (and indeed the ones people have shown that they've done in this Group) have shown that we ... We use Rackspace for other apps. We pay $600 / month for a Quad Xeon, 16GB or RAM, and Raid 5 drive array. Rackspace tech support is 24x7, 1h hardware replacement guaranty. Rackspace manages hardware, OS, backups and we deal only with the app and the database. A server like this can take a huge amount of load... Add $300 / mth for a managed load balancer, add more servers has needed and you get a farm entirely managed by Rackspace tech support. Still not as cool as GAE auto-scalling and HR but close. IMHO, I think that it is key that App Engine pricing accommodate for small apps as well because this is the way to win consumers, consumers being developers in this case. The cloud company that wins them will win the majority of market share (e.g. mysql), but this is more about strategy than pricing. Daniel -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Tue, Sep 6, 2011 at 8:34 PM, Gregory D'alesandre gr...@google.com wrote: Hi Daniel, Thanks for the reply (and sorry to hear you won't be able to make it on Thursday). We are definitely thinking long term and are excited for App Engine to be around long term. In fact, that is the reason we are going through this change now, so that people can start using App Engine without wondering when the plug will be pilled. I'm curious to know which prices you are comparing App Engine's new prices to when you say it is priced out of the market. All of the comparisons we've done (and indeed the ones people have shown that they've done in this Group) have shown that we are actually bringing ourselves in line with the market rather than being drastically cheaper than the market. I completely understand that the new prices are higher than the old prices which is unpleasant (to put it mildly) when you've gotten used to those prices. But I'd be interested in the comparisons you've done on this. Thanks again for your thoughts! Greg On Tue, Sep 6, 2011 at 2:33 AM, supercobra superco...@gmail.com wrote: Thank you for the invite but I am in Austin. :) So here is my input: Last year I co-wrote a book on GWT+GAE with Amy Unruh: http://www.amazon.com/gp/product/1849690448 I wrote that book because I saw something unique and every exciting to App Engine: Google App Engine is a **disruptive technology** as it is the only techno that scales automatically. A disruptive product is a dream for marketers because no competitors come close to this easy-scaling solution. None. Zero. There are left in the dust. So if priced correctly, there should be mass adoption to GAE. Developers will be coming in droves signing up for this awesome product, they won't look at any other solution because App Engine is simple and very affordable. They'll make demos and talks of their new little app running awesomely on App Engine and their friends developers will try App Engine out. However, if priced too high, App Engine will not be adopted. Developers won't run their little app on App Engine but on a competitors platforms and that is what they will demo to their friends and their friends will adopt that competitors technology. So if I was Greg D'Alesandre, I'd look at the long term goal because the race for cloud hosting has started, competition is fierce and with the new pricing **Google priced itself out of the market**. I see two reasons why the new pricing is so high. ** Why is App Engine new pricing so high? 1. because App Engine running costs is high or 2. because App Engine sees a huge opportunity in cloud hosting and wants to make lots of $ now ** Solutions 2. If App Engine wants to make lots of revenue then Greg D'Alesandre should look at the long term as discussed above. Doing some basic 'visioning' I see that most developers will move to cloud hosting and that an affordable entry level pricing is key to adoption. On the long run, Google will make more money with a smaller pricing because there will be mass-adoption. Maybe Google reasoning is: well if you scale your app, you need one or two full time sysadmins to do the load balancing and db replication and this is very expensive, so App Engine is still cheaper than doing it the other way. Correct but this reasoning does not lead to the mass adoption. **Mass adoption in cloud hosting can only happen if the entry level price is painless because competitors have a painless entry level price point** 1. if running costs are high, then the solution is to have more customers so again a smaller price point is the way to be profitable by having more customers. I maybe missing something here because I am not an insider, however... I guess most App Engine developers are missing
Re: [google-appengine] Want to talk to the App Engine team in person?
Thank you for the invite but I am in Austin. :) So here is my input: Last year I co-wrote a book on GWT+GAE with Amy Unruh: http://www.amazon.com/gp/product/1849690448 I wrote that book because I saw something unique and every exciting to App Engine: Google App Engine is a **disruptive technology** as it is the only techno that scales automatically. A disruptive product is a dream for marketers because no competitors come close to this easy-scaling solution. None. Zero. There are left in the dust. So if priced correctly, there should be mass adoption to GAE. Developers will be coming in droves signing up for this awesome product, they won't look at any other solution because App Engine is simple and very affordable. They'll make demos and talks of their new little app running awesomely on App Engine and their friends developers will try App Engine out. However, if priced too high, App Engine will not be adopted. Developers won't run their little app on App Engine but on a competitors platforms and that is what they will demo to their friends and their friends will adopt that competitors technology. So if I was Greg D'Alesandre, I'd look at the long term goal because the race for cloud hosting has started, competition is fierce and with the new pricing **Google priced itself out of the market**. I see two reasons why the new pricing is so high. ** Why is App Engine new pricing so high? 1. because App Engine running costs is high or 2. because App Engine sees a huge opportunity in cloud hosting and wants to make lots of $ now ** Solutions 2. If App Engine wants to make lots of revenue then Greg D'Alesandre should look at the long term as discussed above. Doing some basic 'visioning' I see that most developers will move to cloud hosting and that an affordable entry level pricing is key to adoption. On the long run, Google will make more money with a smaller pricing because there will be mass-adoption. Maybe Google reasoning is: well if you scale your app, you need one or two full time sysadmins to do the load balancing and db replication and this is very expensive, so App Engine is still cheaper than doing it the other way. Correct but this reasoning does not lead to the mass adoption. **Mass adoption in cloud hosting can only happen if the entry level price is painless because competitors have a painless entry level price point** 1. if running costs are high, then the solution is to have more customers so again a smaller price point is the way to be profitable by having more customers. I maybe missing something here because I am not an insider, however... I guess most App Engine developers are missing something here and left disappointed. Greg D'Alesandre: for people who are not in SA, would you discuss your points online? Daniel -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Fri, Sep 2, 2011 at 7:42 PM, Gregory D'alesandre gr...@google.com wrote: Hi Everyone, I know that the pricing changes are challenging and in some ways hard to understand. So, we thought it might help to talk to the App Engine team about it in person, ask us questions you might have, and maybe have a beer with us. If you are interested let us know on the form so we can put you on the list: SIGNUP: https://docs.google.com/spreadsheet/viewform?formkey=dEpzUWdiMU9ZLVlSd0NwSjlHaTFtQVE6MQ WHEN: September 8, 2011 6-9PM PDT WHERE: Thirsty Bear (http://g.co/maps/rmvt) 661 Howard Street San Francisco, CA 94103 Hope to see you there! Greg D'Alesandre Senior Product Manager, Google App Engine -- 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-appengine@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. -- 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-appengine@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.
[google-appengine] Re: GAE pricing is not suited for smaller apps
Personally I don't think it is a slow kill. I think cloud computing is a key business opportunity for Google and that their GAE product is second to none. The Google guys just got the pricing wrong. In fact, if they priced right and added few languages like PHP and Ruby and add a SQL database (SQL is in testing mode now) there would be not a lot of reasons to use AWS or Heroku. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/p48CPFftWeAJ. To post to this group, send email to google-appengine@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.
[google-appengine] GAE pricing is not suited for smaller apps
Good point about small apps I read on this group. Most apps are not intended to be used by hundred of thousands or millions of users so the point that Google makes, i.e. that scalability is what we pay for on GAE, is not relevant for those smaller apps. The vast majority of apps don't need load balancing and therefore a simple AWS server, or Heroku Java setup can do a whole lot of work and are 10x cheaper than GAE. For example our typing race app www.typrx.com runs on App Engine. We are growing the user base constantly but with the new pricing it is really hurting us. I think that Google App Engine won't be the preferred platform for those smaller apps for a pricing like the one they just announced. === Google: Fix this. === -- superco...@gmail.com http://supercobrablogger.blogspot.com/ -- 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-appengine@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.
Re: [google-appengine] Go Language
Go is slower than Java and Java has all the libraries and tools (IDE, debuggers, refactoring, profiling, etc...) that you'll need. Here are the speed test results from a Google study: http://www.readwriteweb.com/hack/2011/06/cpp-go-java-scala-performance-benchmark.php -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sun, Jun 12, 2011 at 6:39 PM, jay kyburz@gmail.com wrote: Hi All, Anybody had a chance to play around with Go yet? My games are CPU heavy because I do a lot of number crunching on game data every time a user requests the game page. This code really has nothing to do with app engine but is pure game code. I would image this code would be significantly faster that Python. Anybody have any experiences to share yet? -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Deploying jsps
I had the same problem. On Windows I just kept the JDK and removed the JRE. On Linux I had to install a JDK package that was missing. What OS do you use? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sun, May 8, 2011 at 9:32 AM, Phil McDonnell phil.a.mcdonn...@gmail.com wrote: I'm deploying my project which contains some jsps. It compiles and runs fine locally. I set it up locally with the jdk instead of the jre to get the jsps to compile locally. When I go to deploy my project through eclipse it says that the jsps won't compile for the deploy I assume that it is linking to the jre still for the deploy instead of the jdk. Does anyone know how to fix this? Error message in eclipse: Unable to update app: Failed to compile jsp files. Thanks so much, Phil -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Deploying jsps
Here is how I solve the same problem on my machine. Go to control panel programs: uninstall all JREs. - Download the latest JDK and install and in what directory the binaries are (e.g. java.exe) - Add this directory path to your PATH variable: in Explorer, right click on your computer and find out where the advance properties are and edit the PATH variable. To check if it works either open eclipse and try again or open a cmd window and run javac -version w/o the quotes. Figure out where it was installed * -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sun, May 8, 2011 at 2:15 PM, Phil McDonnell phil.a.mcdonn...@gmail.com wrote: I'm on windows. Any help you can lend on the configuration of this would be much appreciated! Thanks, Phil On Sun, May 8, 2011 at 12:24 PM, supercobra superco...@gmail.com wrote: I had the same problem. On Windows I just kept the JDK and removed the JRE. On Linux I had to install a JDK package that was missing. What OS do you use? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sun, May 8, 2011 at 9:32 AM, Phil McDonnell phil.a.mcdonn...@gmail.com wrote: I'm deploying my project which contains some jsps. It compiles and runs fine locally. I set it up locally with the jdk instead of the jre to get the jsps to compile locally. When I go to deploy my project through eclipse it says that the jsps won't compile for the deploy I assume that it is linking to the jre still for the deploy instead of the jdk. Does anyone know how to fix this? Error message in eclipse: Unable to update app: Failed to compile jsp files. Thanks so much, Phil -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Re: Prerelease SDK 1.5.0 available for download
+1 -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Thu, May 5, 2011 at 3:25 PM, Mars mars...@askmymob.com wrote: +1 Please give us custom HTTPS :) On May 4, 6:05 pm, Mike mickn...@gmail.com wrote: Hi Ikai A very exciting release!! Congrats. I must say though, I'm dying for custom HTTPS support. Every release I hurriedly read the release notes for it, to no avail. It was slated for preview release last year, but obviously it's now May, and it hasn't arrived When should we be realistically expecting it? Some insights into why it is taking so long would be very much appreciated. For me, it's the final critical thing that AppEngine is missing. Mike :-) On May 4, 1:20 am, Ikai Lan (Google) ikai.l+gro...@google.com wrote: Hey everyone, Prerelease SDK 1.5.0 is ready for download! There are a ton of bug fixes in this release as well as some pretty big features. Check it out. You can get the SDKs here: http://code.google.com/p/googleappengine/downloads/list The release notes are below. You'll notice that they're much longer than usual. We've listed out many of the bugs in the public issues tracker we've addressed. Python == - Support for Backends which allow developers to create infrastructure components that complement the existing dynamic apps which App Engine already provides. Instances of a backend can maintain state, be addressed individually, and are not subject to per-request time limits. They can also be configured to consume more memory and CPU than ordinary dynamic instances. - Task Queues support pull mode, allowing for more control over task queue work rates. To use pull queues, include the 'mode' argument in your queue.yaml. - Pull queues are supported by a REST API, allowing access from outside App Engine. To use the REST API, you must also include a valid ACL section specifying which users can lease tasks from the pull queue. - Task Queue payload limits have been increased. Push queues now support 100KB per task, pull queues support 1MB per task. Within App Engine, the new limit is 32 MB per batch of tasks. With the REST API the limit is 1 MB per batch. - HTTP request and response sizes have been increased to 32 MB. - We have removed the rate quotas for requests, datastore operations, memcache operations, and image API operations. Resource quotas still apply. - When creating new applications, developers will now see the High Replication Datastore as the default configuration option. Developers that still wish to use the Master/Slave configuration must explicitly choose this option at application creation time. - The Task Queue maximum configurable processing rate has been increased to 500/s. - All application Owners, as listed in the Admin Console, can download the app's code, unless code download is disabled for the application. - Added db.py support for making calls to the datastore asynchronously. Available functions are get_async(), put_async(), delete_async(), allocate_ids_async(). Call get_result on the return value of asynchronous datastore functions to block on the call. - Metadata queries can now get all namespaces, kinds, and properties in a given range. - The Testbed API now supports the Channel API. - Users can provide Django settings to be loaded in webapp's django_setup. - Modified Dashboard latency graphs to indicate they only include dynamic requests. - Fixed an issue where Federated User data didn't survive a get-put-delete operation cycle. - Fixed an issue where metadata queries did not support unicode characters. - Fixed an issue where HTTP headers could contain new line characters. - A warning message is shown when the Python version used to run the SDK is different than the Python version used in production. - Fixed an issue with Federated Users causing the Admin Console dataviewer to fail. http://code.google.com/p/googleappengine/issues/detail?id=384 - MacOS and Windows style newlines are now supported for logging in the SDK. http://code.google.com/p/googleappengine/issues/detail?id=560 - Fixed an issue where sending mail with smtp_host set did not work. http://code.google.com/p/googleappengine/issues/detail?id=626 - Fixed the file permissions for appinfo_errors.py and appinfo.py in the SDK. http://code.google.com/p/googleappengine/issues/detail?id=725 - Fixed an issue deploying an app with version set to 0. http://code.google.com/p/googleappengine/issues/detail?id=735 - Fixed an issue where the SDK allowed GET or DELETE with a body, which does not work in production. http://code.google.com/p/googleappengine/issues/detail?id=983 - Fixed an issue where URLFetch/urllib did not work with MacOS and Python 2.6.0-2.6.3.
Re: [google-appengine] Re: Prerelease SDK 1.5.0 available for download
+1 -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Thu, May 5, 2011 at 3:25 PM, Mars mars...@askmymob.com wrote: +1 Please give us custom HTTPS :) On May 4, 6:05 pm, Mike mickn...@gmail.com wrote: Hi Ikai A very exciting release!! Congrats. I must say though, I'm dying for custom HTTPS support. Every release I hurriedly read the release notes for it, to no avail. It was slated for preview release last year, but obviously it's now May, and it hasn't arrived When should we be realistically expecting it? Some insights into why it is taking so long would be very much appreciated. For me, it's the final critical thing that AppEngine is missing. Mike :-) On May 4, 1:20 am, Ikai Lan (Google) ikai.l+gro...@google.com wrote: Hey everyone, Prerelease SDK 1.5.0 is ready for download! There are a ton of bug fixes in this release as well as some pretty big features. Check it out. You can get the SDKs here: http://code.google.com/p/googleappengine/downloads/list The release notes are below. You'll notice that they're much longer than usual. We've listed out many of the bugs in the public issues tracker we've addressed. Python == - Support for Backends which allow developers to create infrastructure components that complement the existing dynamic apps which App Engine already provides. Instances of a backend can maintain state, be addressed individually, and are not subject to per-request time limits. They can also be configured to consume more memory and CPU than ordinary dynamic instances. - Task Queues support pull mode, allowing for more control over task queue work rates. To use pull queues, include the 'mode' argument in your queue.yaml. - Pull queues are supported by a REST API, allowing access from outside App Engine. To use the REST API, you must also include a valid ACL section specifying which users can lease tasks from the pull queue. - Task Queue payload limits have been increased. Push queues now support 100KB per task, pull queues support 1MB per task. Within App Engine, the new limit is 32 MB per batch of tasks. With the REST API the limit is 1 MB per batch. - HTTP request and response sizes have been increased to 32 MB. - We have removed the rate quotas for requests, datastore operations, memcache operations, and image API operations. Resource quotas still apply. - When creating new applications, developers will now see the High Replication Datastore as the default configuration option. Developers that still wish to use the Master/Slave configuration must explicitly choose this option at application creation time. - The Task Queue maximum configurable processing rate has been increased to 500/s. - All application Owners, as listed in the Admin Console, can download the app's code, unless code download is disabled for the application. - Added db.py support for making calls to the datastore asynchronously. Available functions are get_async(), put_async(), delete_async(), allocate_ids_async(). Call get_result on the return value of asynchronous datastore functions to block on the call. - Metadata queries can now get all namespaces, kinds, and properties in a given range. - The Testbed API now supports the Channel API. - Users can provide Django settings to be loaded in webapp's django_setup. - Modified Dashboard latency graphs to indicate they only include dynamic requests. - Fixed an issue where Federated User data didn't survive a get-put-delete operation cycle. - Fixed an issue where metadata queries did not support unicode characters. - Fixed an issue where HTTP headers could contain new line characters. - A warning message is shown when the Python version used to run the SDK is different than the Python version used in production. - Fixed an issue with Federated Users causing the Admin Console dataviewer to fail. http://code.google.com/p/googleappengine/issues/detail?id=384 - MacOS and Windows style newlines are now supported for logging in the SDK. http://code.google.com/p/googleappengine/issues/detail?id=560 - Fixed an issue where sending mail with smtp_host set did not work. http://code.google.com/p/googleappengine/issues/detail?id=626 - Fixed the file permissions for appinfo_errors.py and appinfo.py in the SDK. http://code.google.com/p/googleappengine/issues/detail?id=725 - Fixed an issue deploying an app with version set to 0. http://code.google.com/p/googleappengine/issues/detail?id=735 - Fixed an issue where the SDK allowed GET or DELETE with a body, which does not work in production. http://code.google.com/p/googleappengine/issues/detail?id=983 - Fixed an issue where URLFetch/urllib did not work with MacOS and Python 2.6.0-2.6.3.
Re: [google-appengine] Java GAE/GWT Composite Design Pattern example with Persistence
What are you trying to achieve? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sat, Apr 30, 2011 at 8:06 PM, RH richkh...@gmail.com wrote: I'm looking for a simple way to persist a set of dynamic Composite Design Pattern objects (as described in Design Patterns by Gamma, Helm, Johnson, and Vlissides) with either Google's native datastore, JDO, or JPA, as well as send to and from the client via RPC. I've yet to figure a way to send a complex composite structure from client to server, persist it in the datastore, and retrieve all or part of it again at the client side. Is this even possible? I'm sure this is a common scenario, but I've yet to figure out a way with GAE and GWT RPC. Nor have I run into anyone either trying it or with a similar solution. Any suggestions or ideas out there? Thanks, -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] gae needs a counter service
+1. Totally needed. On Mar 16, 2011 12:25 AM, David Keyes keyes...@gmail.com wrote: Been using gae/j for a while now. One big missing piece IMO is a service that would allow me to manage global distributed counters. Yes I know that there are patterns for doing this (e.g. sharding), but it is such a common use case that I think a highly optimized service would be ideal. The perfect solution would allow me to have read-only access to the counters via the datastore. Thoughts? -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Channel API future improvements?
+1 for updating the roadmap. -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Thu, Feb 3, 2011 at 9:16 PM, James Broberg jbrob...@gmail.com wrote: Slightly OT but the roadmap could sure do with an update. A couple of those Features on Deck are already in the current SDK. On 4 February 2011 07:55, Ikai Lan (Google) ikai.l+gro...@google.com wrote: In general, we don't make comments on upcoming features. You are welcome to check the roadmap for updates: http://code.google.com/appengine/docs/roadmap.html While we're planning Channel API improvements, have you looked into providers such as beaconpush.com or pubnub.com? If there's a product you are looking to build, you should take a pragmatic approach and look into what'll work instead of being blocked waiting on features that need to be implemented. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Feb 3, 2011 at 10:36 AM, Peter Petrov onest...@gmail.com wrote: Today there was a GAE SDK 1.4.2 prerelease. I was quite disappointed that it had no Channel API related updates/improvements in the release notes. Since there is also no official roadmap announced for the Channel API, can we get some unofficial update about the features and improvements coming in the near/distant future? Here is a short wishlist from me: 1. Batch send method (efficiently fan-out one message to a potentially large number of channels). Moishe said this was planned some time ago. 2. Channel presence (connect/disconnect notifications to the application). This is also being worked on according to Moishe. 3. Charge CPU on channel disconnect time, instead of token creation time. This would allow us to pay for the actual usage, instead of the current fixed 2-hour tokens, which require us to implement complex and imperfect token reuse schemes. Hopefully this shouldn't be too hard to implement given that you are already working on disconnect notifications. 4. Direct access to the lower Channel API layers for non-browser based clients, bypassing the JavaScript long-polling Comet layer. E.g. something like allowing a client to connect via XMPP to channel...@appspotchannel.com using the channel_token as password. Any status updates regarding these or other planned improvements would be appreciated. Thanks! -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Re: How to launch 100K+ recurring task every 5 min
An easy way to avoid this is to kick off a batch of asynchronous URLFetch requests, wait for all of them to complete, then put the results to the datastore in a single batch put. That's a good idea. Glad it is also available in Java. Daniel -- 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-appengine@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.
Re: [google-appengine] Re: How to launch 100K+ recurring task every 5 min
The countdown parameter of TaskQueue is indeed a big help here. Thanks for pointing that out. -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Fri, Jan 14, 2011 at 3:41 PM, Uros Trebec uros.tre...@gmail.com wrote: re On Jan 14, 7:24 pm, supercobra superco...@gmail.com wrote: One of the challenge is to wait for 5 minutes. E.g. Fetch a URL, store results, wait 5 min, do it again. Since a queue will execute the task almost immediately (if it is empty) this would not work unless the queue is filled w/ a known number of tasks. Any suggestion welcome. You can use the 'countdown' parameter in Task constructor ( http://code.google.com/appengine/docs/python/taskqueue/tasks.html#Task ) to set the number of seconds for the Task to wait in the queue before executing. I use this for scheduling a task a few minutes in the future when UrlFetch returns the data I already have. lp, Uros -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] How to launch 100K+ recurring task every 5 min
Hello again, Again as Eli mentioned, to offer any solutions we'd need to know what you're trying to do in all those tasks. We are exploring the idea of migrating our website monitoring service Montastic (www.montastic.com) to GAE. Right now it works on MySQL but scalability becomes challenging and we need to explore a re-architecture of our system. GAE would be ideal if it was possible. So we do need to do a LOT of UrlFetch-es every 1, 2, 5 minutes. One of the challenge is to wait for 5 minutes. E.g. Fetch a URL, store results, wait 5 min, do it again. Since a queue will execute the task almost immediately (if it is empty) this would not work unless the queue is filled w/ a known number of tasks. Any suggestion welcome. Daniel -- 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-appengine@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.
Re: [google-appengine] silent-auction type application
ikai.l+gro...@google.com says The solution here is, again, to shard the timestamp by prefixing a value to distribute the writes. It seems that sharded counters are needed in many cases. Could Google develop a shared counter capability built into GAE that developers could use out of the box? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Fri, Jan 14, 2011 at 12:05 PM, Ikai Lan (Google) ikai.l+gro...@google.com wrote: You can certainly write to Memcache, but I don't think your application can tolerate any kind of volatility. Persistence is the price you have to pay. Fortunately, I think this can be done pretty cheaply. Just be aware of monotonically increasing indexes like timestamps: if you have an application with a high write rate that has a timestamp, this will cause the persistence unit storing the indexes to be unable to be autosplit easily across multiple hardware instances and you will take a performance hit. The solution here is, again, to shard the timestamp by prefixing a value to distribute the writes. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Fri, Jan 14, 2011 at 6:06 AM, Richard Arrano rickarr...@gmail.com wrote: I'm looking to make a silent-auction type of application where you have 20-30 users bidding on an item at a time, with potentially hundreds or thousands of auctions happening simultaneously. As soon as a high bid is made, it updates this information and sends it via the Channel API to the other users in the auction. I see two potential difficulties: 1. The limit on updating an entity group about once per second - I believe this can be solved with sharding bids amongst users in the auction and querying all shards to find the maximum bid at any given time, correct? 2. The nature of the auction lends itself to a heavy amount of writing to the datastore - this itself eats up CPU and I’m trying to figure out if it can be avoided. Is this just inevitable in this type of application? Does it matter that I would only be only updating a single IntegerProperty() in any given write? Is there some clever solution that we can apply that avoids the hammering of the datastore? Any tips or suggestions would be appreciated. Thank you, Richard -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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.
Re: [google-appengine] How to launch 100K+ recurring task every 5 min
Hi Eli, Thanks for the great feedback. If Task Queue Java is as evolved as Phyton that maybe the way to go. -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Fri, Jan 14, 2011 at 12:52 PM, Eli Jones eli.jo...@gmail.com wrote: You should probably start experimenting with the Taskqueue to get a better idea how it functions and what is possible. When you create a Task.. you can define a countdown or eta value.. so, the task gets added.. but it is scheduled to execute at a future time (not immediately). So, you can just create a named, chained task that does a batch of URLfetches asynchronously with a callback (not sure how many can be done at once, one way to find out is to test it.).. and once it is done gathering and putting data.. it schedules the next 5 minute batch. http://code.google.com/appengine/docs/python/urlfetch/asynchronousrequests.html See Nick Johnson for an overview of how to do chaining with deferred (I personally prefer regular Taskqueue, but deferred has its positive aspects): http://blog.notdot.net/2010/03/Task-Queue-task-chaining-done-right You could also have a cron job that creates all of your scheduled tasks for the day at once. Depending on if there would be no issues with some tasks not finishing before the next 5 minute task. On Fri, Jan 14, 2011 at 1:24 PM, supercobra superco...@gmail.com wrote: Hello again, Again as Eli mentioned, to offer any solutions we'd need to know what you're trying to do in all those tasks. We are exploring the idea of migrating our website monitoring service Montastic (www.montastic.com) to GAE. Right now it works on MySQL but scalability becomes challenging and we need to explore a re-architecture of our system. GAE would be ideal if it was possible. So we do need to do a LOT of UrlFetch-es every 1, 2, 5 minutes. One of the challenge is to wait for 5 minutes. E.g. Fetch a URL, store results, wait 5 min, do it again. Since a queue will execute the task almost immediately (if it is empty) this would not work unless the queue is filled w/ a known number of tasks. Any suggestion welcome. Daniel -- 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-appengine@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. -- 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-appengine@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. -- 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-appengine@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.
[google-appengine] How to launch 100K+ recurring task every 5 min
Hello there, I am looking for ideas. I want to perform 10 recurring activities every 5 minutes. Each activity takes about 5 seconds. I think using 5-min cron to start 100k+ jobs would not be cpu/cost effective. Any ideas on how to do this w/ the least overhead? Daniel -- 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-appengine@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.
Re: [google-appengine] Help desk app
Mojo Helpdesk is integrated with Google apps and receives email, create tickets, set ticket status, etc... Not on GAE yet but fully integrated with single sign on and Google accounts. www.mojohelpdesk.com On Mon, Dec 20, 2010 at 7:35 AM, Richard richar...@gmail.com wrote: Have any open source help desk apps been built for GAE? Something that receives emails, creates a ticket, send replies, set ticket status, etc -- 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. -- 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.
Re: [google-appengine] Help desk app
Could you describe what you are trying to achieve? On Mon, Dec 20, 2010 at 9:11 AM, Richard Baron Penman richar...@gmail.com wrote: yes there are many proprietary paid help desk systems like mojo, but that's not what I'm after. Is there atleast an email app running on GAE, which I could integrate tickets with? On Tue, Dec 21, 2010 at 1:05 AM, supercobra superco...@gmail.com wrote: Mojo Helpdesk is integrated with Google apps and receives email, create tickets, set ticket status, etc... Not on GAE yet but fully integrated with single sign on and Google accounts. www.mojohelpdesk.com On Mon, Dec 20, 2010 at 7:35 AM, Richard richar...@gmail.com wrote: Have any open source help desk apps been built for GAE? Something that receives emails, creates a ticket, send replies, set ticket status, etc -- 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. -- 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. -- 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. -- 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.
Re: [google-appengine] Re: my app has been disabled
I would be surprise it Google shut you down because of a competing factor. Let's see what they say. Just curious, did you enable billing on your app? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sat, Dec 18, 2010 at 7:09 AM, ajaxer calid...@gmail.com wrote: badly concerned -- 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. -- 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.
Re: [google-appengine] Using datastore for up to 4.5 billion keys
Just curious, what is this huge database about? Can we check it online? -- superco...@gmail.com http://supercobrablogger.blogspot.com/ On Sat, Dec 18, 2010 at 7:20 AM, Donovan Hide donovanh...@gmail.com wrote: Hi, I have a custom index of a large amount of content that works by creating a 32 bit hash for sections of text. Each document id is stored against this hash and lookups involve hashing the input and retrieving the matching ids. Currently I use node.js to serve the index and hadoop to generate it. However this is an expensive operation in terms of processing and requires an SSD drive for decent serving performance. The scale of the index is as follows: Up to 4.5 billions keys An average of 8 document ids per key, delta-encoded and then variable integer encoded. Lookups on average involve retrieving values for 3500 keys Having read the datastore docs it seems like this could be a possible schema: from google.appengine.ext import db class Index(db.Model): hash=db.IntegerProperty(required=True) values=db.BlobProperty(required=True) I would be grateful if anyone could give me some advice or tips on how this might perform on AppEngine in terms of query performance, cost and minimizing metadata/index overhead. It sounds like 4.5 billion*metadata storage could be the killer. Cheers, Donovan -- 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. -- 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.
Re: [google-appengine] downloading source code with 1.4.0 fails with a 403, but I'm the only maintainer!
The account consolidation could be the issue. Try to use another browser with a fresh login or clear all your cookies. Daniel Guermeur -- superco...@gmail.com Co-author of App Engine Java and GWT Development: http://bit.ly/hdTHyB Blog: http://supercobrablogger.blogspot.com/ On Fri, Dec 3, 2010 at 8:38 PM, Ben Adida b...@adida.net wrote: subject says it all: I'd like to download the code for an older app I haven't touched in a while, but need to update. When I try to download, I get a 403 saying I'm not allowed to download this version. The documentation seems to indicate that this happens when another developer uploaded that version... but I'm the only developer who uploaded anything! In the interim, I have consolidated two google accounts, so I suppose this could be the issue, but then I'm not sure how to resolve this. Help? -- 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. -- 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.
Re: [google-appengine] Channel API question
Every client needs to have its own server channel. To create a chat, you create one channel per client and a table that contains people chatting. Each time a message is received on the server, the server needs to push it to other chat participants. -- superco...@gmail.com Co-author of App Engine Java and GWT Development: http://bit.ly/hdTHyB Blog: http://supercobrablogger.blogspot.com/ On Sat, Dec 4, 2010 at 4:25 AM, alon alon.car...@gmail.com wrote: Hey, After reading the documents im a tad unclear on how the whole process of channel api works in terms of sharing the messages between clients. User A opens a channel, i create a channel on datastore for that user and return the channel id to the javascript part. User opens a socket and listens. User B Opens a channel, i check if a channel is created already, if so it returns the existing channel id (same for user A) and returns it to the javascript, user opens a socket and listens. Is that the correct method? How can i share messages between clients? i saw that you combine the userid in the channel id returned. some clarification on that? How do i create a simple chat between users that share the same chat room? -- 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. -- 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.
Re: [google-appengine] Amazon AWS vs Google App Engine
Amazon and Google have been long-time partisans of freedom of speech. However in this case, the pressure coming from the government must be incredible. Amazon is not the only victim of these intimidations. US government employees have been forbidden to visit Wikileaks sites and to discuss these matters on Facebook. At least one US university has been 'persuaded' to ask their students not to reference any Wikileaks documents in their research papers... (how is that for doing thorough research!). Even crounties bend under US pressure. We have seen it to be the case with Spain Germany which dropped their lawsuits, investigations and enforcement of arrest warrants for torture and kidnappings (renditions) after the US pressured them (source Wikileaks cables). So I would assume that Google or any organization would probably comply as well. To ensure free speech can not be prevented by taking down web sites, we need to create a totally distributed website hosting technology based on BitTorrent or something similar. Happy coding. ;-) Daniel Guermeur -- superco...@gmail.com Co-author of App Engine Java and GWT Development: http://bit.ly/hdTHyB Blog: http://supercobrablogger.blogspot.com/ On Fri, Dec 3, 2010 at 5:18 PM, nickmilon nickmi...@gmail.com wrote: There is a lot of talk and flame wars going on AWS vs GAE topic, up to now all this talk was concentrated on technical and economic issues. News of Amazon throwing away the WikiLeaks website has raised new arguments on the cloud battlefront. So I want to raise here the hypothetical question what would be the fate of WikiLeaks if it was hosted on App Engine ? (For obvious reasons I do not expect a definite yes/no answer from Google's team, but may be I am wrong) Happy coding:-) Nick -- 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. -- 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.
Re: [google-appengine] Re: Channel API quota
We definitively need more than 100K. Each time a user open close his / her browsing session it is counted as 1 channel creation. I open and leave Gmail, and open new windows at least 50 / 100 times a day. So if 1000 users use an app like I use Gmail then it makes about 100K channel api creation / day for them. Based on this calculation, I think 100 channel api creations / day is a good starting number. So if my app has 30,000 users I'll need 3m slots... I think the challenge for Google is the long running - for nothing - connection for example like when you leave your browser open and go to lunch or home for the evening -- superco...@gmail.com Co-author of App Engine Java and GWT Development: http://bit.ly/hdTHyB http://supercobrablogger.blogspot.com/ On Fri, Dec 3, 2010 at 3:22 PM, Rafael Sierra rafaeljs...@gmail.com wrote: On Fri, Dec 3, 2010 at 7:15 PM, Geoffrey Spear geoffsp...@gmail.com wrote: On Dec 3, 12:57 pm, Peter Petrov onest...@gmail.com wrote: For billing-enabled apps the quota is 95040 channels created per day. This is still extremely low, I completely agree. If I remember correctly, yesterday after the 1.4.0 release this quota was considerably higher (about 10 times). Probably they are having capacity problems with the GAE / GTalk infrastructure. Some official explanation would be nice, though. The Channel API isn't even listed on the Quotas page yet ( http://code.google.com/appengine/docs/quotas.html ), but it's not unreasonable to believe there will be an option to request an increase like there is for the other fixed quotas that are listed there. It is for me: Channel Channel API Calls 0% 31,574 of 91,995,495 Okay Channels Created 2% 1,815 of 95,040 Okay Channel Data Sent 0% 0.00 of 2,088.13 GBytes -- 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. -- Rafael Sierra http://blog.rafaelsdm.com -- 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. -- 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.
[google-appengine] appengine.google.com: error 500
I am getting error 500 going to: http://appengine.google.com/a/metadot.com -- Daniel Try a typing race with Typrx (GAE + GWT): http://app.typrx.com -- 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.
Re: [google-appengine] Re: Using GAE for a REST API
Hello there, What is your best practice to develop REST on GAE? Daniel -- superco...@gmail.com On Wed, Nov 24, 2010 at 2:36 PM, Jay jbaker.w...@gmail.com wrote: Yahel, GAE is a great platform for building and delivering RESTful services. Of course there are quotas. But you are in control of how much quota you want to a large extent. On Nov 23, 9:43 pm, Yahel Carmon yah...@gmail.com wrote: Hi all, I'm new to playing with GAE, and I'm thinking of using it to build a very simple API for one of my projects. I like the idea of the scaling (mostly) handling itself for an API. However, I've read things about things like rate limiting triggering captchas for end users, a la Google services. Does that type of rate limiting present problems with using GAE as a backend for a REST API? I apologize if I'm asking a dumb or obvious question, but its surprisingly difficult to Google for if GAE can be used to build APIs without finding pages* *about GAE's API. Thanks in advance! -- Yahel Carmon (917) 445-3498 Twitter:http://twitter.com/yahelc Facebook:http://facebook.com/yahel LinkedIn:http://www.linkedin.com/in/yahelc -- 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. -- 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.
Re: [google-appengine] Let's defend GAE!
At would concur with most criticisms. Developing on GAE is chall-engine. :) However I stick to GAE because I think that many of the limitations are temporary and that platform as a service is the way to go. When scaling the advantages outnumber the disadvantages by an order of magnitude. I prefer hiring 2 additional developers who are going to do the back-flips GAE requires (and it does) once and for all rather than employing an army of sysadmins who are going to tweaks load balancers, app servers, and db replicas on an ongoing basis for the rest of their employment life. Daniel -- superco...@gmail.com On Sun, Nov 21, 2010 at 9:02 PM, Vanni.T vanni.tot...@gmail.com wrote: Hey guys, this post (Goodbye, Google App Engine) is #1 (201 points in 5 hours) on Hacker News: http://www.carlosble.com/?p=719 http://news.ycombinator.com/item?id=1927903 It is a horrible, uninformed anti-GAE article. Too many you're right, GAE sucks comments out there for my taste. Nothing to say? -- 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. -- 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.
Re: [google-appengine] Re: Early Christmas Present from Google?
Kudos Google. My typing race app now flies again. http://app.typrx.com -- superco...@gmail.com On Sun, Nov 7, 2010 at 8:55 AM, Joshua Smith joshuaesm...@charter.net wrote: +1. Simple amazing, across all my apps. Where do I send the case of beer? (Or would a box of k'nex be a better choice?) -- 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. -- 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.
Re: [google-appengine] Instance maximum number of requests
Just curious, do you guys retire instances after around 10k requests to avoid memory leaks? -- superco...@gmail.com On Wed, Oct 27, 2010 at 6:50 PM, Ikai Lan (Google) ikai.l+gro...@google.com wrote: Yes. Application instances are meant to be relatively short lived. Once each instance has served a certain amount of requests, we will gracefully terminate it and spin up a new instance to take its place. The number of requests to trigger this limit is subject to change for performance tuning reasons, but it should be in the ballpark of tens of thousands of requests. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Wed, Oct 27, 2010 at 1:50 PM, nickmilon nickmi...@gmail.com wrote: I was doing some load tests on app engine today when I noticed a new Info message in the logs: After handling this request, the process that handled this request reached the maximum number of requests that may be handled in a single process' lifetime, and exited normally. So what that supposed to mean ? Up to know we new that application instances are automatically terminated after some inactivity time out. If I understand this message well now we know that a process can be terminated after handling so many requests. How many exactly ? is this a new magic number ? Lets hope we will have some answers from the always helpful App Engines team. -- 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. -- 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. -- 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.
Re: [google-appengine] Re: The server encountered an error ?
We experience lots of timeouts too. I think Google guys are trying to upgrade their infrastructure during the nights and we see some side effects... -- superco...@gmail.com On Wed, Oct 27, 2010 at 10:04 PM, Sundar cyberto...@gmail.com wrote: Would a state of elevated for datastor or task queues affect deployments? I'm unable to deploy my app. On Wed, Oct 27, 2010 at 11:02 PM, blackpawn pharmapsycho...@gmail.com wrote: yep me too. system status says there is an Anomaly with the Datastore that is being investigated. :O -- 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. -- 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. -- 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.
Re: [google-appengine] Re: The server encountered an error ?
Awesome. -- superco...@gmail.com On Wed, Oct 27, 2010 at 10:24 PM, Raymond C. windz...@gmail.com wrote: Thanks GAE team for the quick action~ On Oct 28, 11:12 am, Sundar cyberto...@gmail.com wrote: And now it's all ok. It's amazing how well it works when it does, and how I have crazy anxiety when things go wonky on GAE :) On Wed, Oct 27, 2010 at 11:04 PM, Sundar cyberto...@gmail.com wrote: Would a state of elevated for datastor or task queues affect deployments? I'm unable to deploy my app. On Wed, Oct 27, 2010 at 11:02 PM, blackpawn pharmapsycho...@gmail.comwrote: yep me too. system status says there is an Anomaly with the Datastore that is being investigated. :O -- 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.comgoogle-appengine%2Bunsubscrib e...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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. -- 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.
Re: [google-appengine] Re: Uploading Indexes - Server Error
I got the same this weekend. Was gone after few hours... -- superco...@gmail.com On Mon, Oct 25, 2010 at 10:08 PM, Stephen Johnson onepagewo...@gmail.com wrote: I'm getting the same error, but with Java. Also, clicking on Indexes in Dashboard goes to error page. Stephen The error during deploy is: Unable to update app: Error posting to URL: https://appengine.google.com/api/datastore/index/add?app_id=APPIDversion=VERSION; 500 Internal Server Error Server Error (500) A server error has occurred. On Mon, Oct 25, 2010 at 7:49 PM, Eli Jones eli.jo...@gmail.com wrote: Oh, the error message it shows when I run appcfg.py update is: Your app was updated, but there was an error updating your indexes. Please retry later with appcfg.py update_indexes. On Mon, Oct 25, 2010 at 10:48 PM, Eli Jones eli.jo...@gmail.com wrote: I am able to update my app code with appcfg.py update.. but it always throws an error when it gets to the upload indexes part. If I try to only update_indexes, I keep getting the error as well: Server: appengine.google.com. Uploading index definitions. Error 500: --- begin server output --- Server Error (500) A server error has occurred. --- end server output --- I presume this is a transient issue and will be cleared up soon.. but I have nothing else to do while I wait.. so I am posting a message here in case some bored soul is watching the list. -- 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. -- 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. -- 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.
