A quick and simple app I wrote to learn Golang and GAE. Well, I build a
few smaller pointless apps and then dove right into this. Loved how simple
GAE is to use and really like using Go.
Basically, the app helps you keep track of your stuff so you can throw out
the sticky notes you lose any
independent (not
exactly the same) other projects...a slight gray area in the ToS.
Project has been pulled from Github, blog post has been redone, appengine
project disabled.
Corey
--
You received this message because you are subscribed to the Google Groups
"Google App Engine"
independent (not
exactly the same) other projects...a slight gray area in the ToS.
Project has been pulled from Github, blog post has been redone, appengine
project disabled.
Corey
--
You received this message because you are subscribed to the Google Groups
"Google App Engine"
Hi All,
I build a method for load balancing on GAE.
Why?: Yes, I understand that GAE auto scales on application demand.
However, it does not balance in the sense of free quota usage. If your
free quota app hits the quota limit, wouldn't it be nice to just use
another project and that projec
Ikai Lan, any suggestions or are we just SOL?
--
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..
I believe the only small operations are (a) getting a key from an
index in a query, and (b) allocating a new key.
(b) doesn't come up too often for me but (a) is useful in reducing
Database Read costs by allowing me to grab the keys for a query
(already sorted) before actually getting the entity c
In my experience the pricing for hobby apps is quite good and in
general you'll find that light usage will fall under the free quota.
If you decide to go to production, the heavy costs come in a couple
forms:
- datastore reads/writes
- storage costs
- frontend instance costs
How much each of
We've had similar needs. We typically create an API (and shared
secret) on the remote server that App Engine calls (or vice versa).
If you want to update the two systems independently you just need to
maintain backwards compatibility for a time.
For example, let's say AppEngine is your frontend a
Johnson, could you please elaborate a bit? Are you suggesting that
AppEngine provide a way to buffer the index updates or that there's
already a way to do that?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send em
please describe the engineering details and business purpose
Provided in an earlier post. Do you need any more info? Any
thoughts? We tried registering for Premier support a few days ago but
haven't heard back yet.
Thanks again,
-Corey
On Jan 6, 8:50 am, George wrote:
> Corey
if we treat the geobox update as a one-time cost, we have other
properties like scores, labels, etc that require occasional tweaking.
Updating even a single indexed property across all these entities
costs us $60-$100 and typically many times that in practice because
these interesting fields tend to b
I am using the bulkloader to move data from one App Engine app to
another (server-hosted app or local dev). I've got the configuration
file setup and the datastore entities migrate nicely, but I'm having
trouble migrating the blobstore files.
Assuming I can pull down all the blobstore files from
Rats! Scuppered the subject. Sorry about the re-post!
Has anyone succeeded in using z3c.rml with AppEngine yet? I've got a need
to create a complex and long document that something like a z3c.rml would be
much handier.
I've spent the best part of today trying (in vain) to get it simply working
Has anyone succeeded in using z3c.rml with AppEngine yet? I've got a need
to create a complex and long document that something like a z3c.rml would be
much handier.
I've spent the best part of today trying (in vain) to get it simply working
on my windows command line, much less from within the SD
14 matches
Mail list logo
