On Fri, Feb 12, 2010 at 8:33 AM, ryan <[email protected]<ryanb%[email protected]> > wrote:
> On Feb 11, 3:08 pm, phtq <[email protected]> wrote: > > > > Looking at our error logs for the last 2 days, I would have to save > > the situation is improved with the advent of 1.3.1, but certainly not > > fixed. From the standpoint of our app., being forced to supply all our > > mp3, png, etc. files out of the database enormously increases our > > exposure to the timeout 'feature'. > > i definitely agree, serving static files from the datastore is far > from optimal. the 1000 file limit is definitely something we're aware > of and still actively thinking about, but i don't have any updates on > that right now. > I think you mean the 3000 file limit. :) -Nick > > having said that, if these truly are static files that don't change, i > assume you're caching them in memcache and usually serving from there, > as opposed to serving them from the datastore on every request...? > > also, if they're static files, the blobstore api would be much more > appropriate than the datastore. have you tried it? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
