Allowing the resizing of images greater than 1Mb is huge. We've spent an
incredible amount of time and money trying to work around this with limited
success. If AppEngine supported this we wouldn't have to worry about it.
- ryan.
On Wed, Oct 14, 2009 at 9:19 AM, Andy Freeman ana...@earthlink.net
Also, naked domains
On Oct 14, 8:19 am, Andy Freeman ana...@earthlink.net wrote:
2) Allow resizing images that are bigger than 1 Mb
http://code.google.com/p/googleappengine/issues/detail?id=1422
Yes! There's no point in adding image support to my application
without the ability to
1. Full-text search
2. Incoming email
3. HTTPS on Google Apps
--~--~-~--~~~---~--~~
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
1. WordPress support
http://code.google.com/p/googleappengine/issues/detail?id=124
2. Klingon support
http://code.google.com/p/googleappengine/issues/detail?id=2134
3. COBOL and Lolcats support
http://code.google.com/p/googleappengine/issues/detail?id=150
nah. i am kidding.
My top three issues (in descending order of stars):
1) Support for the Python Image Library:
http://code.google.com/p/googleappengine/issues/detail?id=38
2) Support for NumPy (Numeric Python):
http://code.google.com/p/googleappengine/issues/detail?id=190
3) Support for lxml:
1. Full text search
2. Memcache objects that get a chance to write themselves to disk if
being evicted (yes, this would require some changes to the memcache
allocation approach)
3. Faster cold start with Django (I think there are many apps pinging
themselves constantly to try to overcome this
Agreed. I would argue however that the same economics affecting our
situation affect Google. Whether an SLA is in place or not, if App
Engine gets a reputation for being down all the time, an SLA will
hardly matter.
As for my issue, as a person who runs (I'm guessing) a high-volume
site
Well, here's the reasons I'm not using appengine for my big project,
so I guess these would be my top issues
1. datastore timeout issue... we need way more reliability with the
datastore. timeout on put can be abstracted with memcache (provided
the memcache entity can last long enough for a
My only issue : More reliable datastore.
So that I don't have to put a thousand try catch There is a
setting entity in my app. It changes exactly twice a week by crons and
is read around 3000 times a week. However for NO REASON around 10
( read few ) of them will fail when fetching with
1. CPU cost of datastore writes. This is by far the biggest show-
stopper for any data centric application. GAE is just to expensive!
2. The missing java.awt.* classes that is needed to get FOP/iText PDF
generation. Another show-stopper for most enterprise applications.
3. HTTPS. Any serious
1) Subdomain and domain management API
(http://code.google.com/p/googleappengine/issues/detail?id=2214 and
http://code.google.com/p/googleappengine/issues/detail?id=113)
It's a Google Apps issue, but very related to GAE. We can't have
http://my-customer-id.my-domain.com without manual
Based on my own experience and what I have read here the past 18
months I recently published this:
Is GAE ready for prime time? at http://www.gae123.com/articles/gaerd/
Read it and let me know if I miss soemthing major or I am overstating
something with direct e-mail.
Thanks
PS The
1. Bugfixing (especially Java SDK bugs)
2. Enable queries with multiple sortings or find a way to iterate over
all entities without loosing a sort attribute for __key__
3. Delete entities by query without manually fetching keys and passing
them back and a real delete * from kind
On 7 Okt.,
To people who feel that an SLA is important, I would remind you that
for any serious site, the major cost of downtime is lost availability,
lost business, customer dissatisfaction, etc. A hundred dollar
reimbursement for an hour of downtime is of no consequence. For this
reason, SLAs are not
Second allowing resize of larger images. Also, it'd be great to have
image optimization. It's a given using ImageMagick or similar for a
web-based app that one has the option of both scaling, cropping, etc,
and compressing. It wouldn't have to be more cutting-edge PNGCrush
type stuff just
1. Full Text Search
2. Fix the over 100 indexes issue (server error 500)
3. Easier import / export from the datastore, and mass entity
deletion
On Oct 6, 4:08 pm, Ben Regenspan bregens...@gmail.com wrote:
Second allowing resize of larger images. Also, it'd be great to have
image
Good point. But I don't think of an SLA as the reparations that will
be made in case of breach of the SLA, more that is implied that those
service levels will, for the most part, be met.
Currently maintenance is scheduled in the middle of prime time,
support is best effort, and quality is
I was one of the ones who starred C# support since C# has LINQ. LINQ
gives you joins and aggregations, two features that are really needed
in the app engine.
C# is a serious request.
On Oct 6, 10:04 am, Kenneth goo...@kmacleod.ie wrote:
I was looking at the issue list the other day. There is
mine are...
1) Built-in Paging (no issues, but it's in roadmap and coming soon)
Currently we have to re-implement or re-think paging for every situation.
2) Full-text search API
(http://code.google.com/p/googleappengine/issues/detail?id=217)
No-brainer. Much needed and required by almost all
On Tue, Oct 6, 2009 at 6:04 AM, Kenneth wrote:
1) More granular accounting of how datastore space is used
http://code.google.com/p/googleappengine/issues/detail?id=1396
This one should be easy, the information is being pulled from
somewhere already. Right now storage usage is a total black
My top top issues are...
1) SSL/HTTPS Support on Google Apps domains
http://code.google.com/p/googleappengine/issues/detail?id=792
I couldn't agree more. This is a huge problem for people who want to
develop real e-commerce applications. If Google wants to encourage and
grow their paid
1) Full text search
2) Full text search
3) Incoming email handling support
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
1. User login from multiple Google Apps domains, or deployment across
multiple Google Apps domains.
2. BOSH transport (layer under XMPP) for transparent server-to-client
messaging.
3. Full text search.
On Oct 6, 10:16 am, vivpuri v...@vivekpuri.com wrote:
1. Billable Task Queue API.
2.
1) DataStore Timeout
2) Full Text : attribute and Document Full Text (word, excel)
3) New billing options (monthly, Euro,...) :
http://code.google.com/p/googleappengine/issues/detail?id=1999
On 6 oct, 11:04, Kenneth goo...@kmacleod.ie wrote:
I was looking at the issue list the other day. There
Second to Full text search
Second to Timeout
Second to SSL
--~--~-~--~~~---~--~~
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
define 3in1 workui integrated vcs,edits and deployments
http://code.google.com/p/googleappengine/issues/detail?id=2136
internationalisation and localisation
http://code.google.com/p/googleappengine/issues/detail?id=2134
3rd, use yaml for everything trivial
1) More efficient writing/reading to/from the datastore. Currently
its too expensive in terms api_cpu.
This would make GAE much more suited to dynamic apps that write/read
the datastore regularly.
2)Built-in Paging
3) SSL/HTTPS support
--~--~-~--~~~---~--~~
1) _Efficient_ writing/reading to/from the datastore, it is _way_ too
expensive in terms api_cpu.
2) User login from multiple Google Apps domains, or actual deployment of an
app to multiple Google Apps domains so I do not need a separate app for each
client.
3) SSL/HTTPS Support on Google Apps
1) More control over how Memcache evict entries. More information on
Memcache usage (how big, how many entries, how it scale with more
traffic). Allow us to purchase more memcache space/slots? Allow us to
run some code, call some url, or write data to datastore upon
eviction. Basically, anything
1. XMPP and WebSockets
2. XMPP and Flash
3. XMPP and ways to connect to our bots from inside the browser.
On Oct 6, 5:04 am, Kenneth goo...@kmacleod.ie wrote:
I was looking at the issue list the other day. There is a lot rubbish
in there (support c#!) but what do people who are actively
1. SSL for custom domains.
2. Reliability. What's disturbing is that the same application can
work reliably for a while, then it starts working unreliably - based
on changes Google makes on the server.
3. A online backup methodology: the ability for us to maintain
snapshots of our data, with
31 matches
Mail list logo
