I'm not quite sure what is that you are looking for, but appengine is not intended to be used as storage, it is intended for full on applications. With that said, you can freely set any headers you please by writing your own URL handler in Python.
On Dec 9, 11:10 am, jago <[EMAIL PROTECTED]> wrote: > Well partially. Obviously I would prefer compressing the file by a > factor 10 and then send less data, without setting the right content- > encoding this is impossible though. > > Bigger files would at least not totally invalidate appengine for my > use. Still it is no replacement for the content-encoding feature. > > On Dec 9, 9:59 am, Thomas Johansson <[EMAIL PROTECTED]> wrote: > > > Hi jago, > > > As per the roadmap (http://code.google.com/appengine/docs/ > > roadmap.html); "Service for storing and serving large files" will be > > coming in the October '08 - March '09 timeline. That should solve your > > problem, if I'm not mistaken? > > > Personally, I hope that applies to regular old static content and code > > as well, ideally including lifting the 1.000 file limit, but probably > > not. > > > On Dec 9, 8:43 am, jago <[EMAIL PROTECTED]> wrote: > > > > I would like to host an applet on appengine. Still either I compress > > > the jars with pack200 which brings the size of each jar well below 1MB > > > but then I have no content-encoding. Or, I don't compess the jars and > > > hit the 1MB filesize limitation. > > > > AppEngine really has become frustrating. There are just too many > > > limitations. Will this ever change? > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
