Huh. Never seen this before, I do apologise for the confusion. That really should be documented clearly somewhere that isn't specific to one of their libraries, as that seems to be a core limitation.
Again, sorry for the confusion. On Dec 9, 8:44 pm, "Barry Hunter" <[EMAIL PROTECTED]> wrote: > 2008/12/9 Thomas Johansson <[EMAIL PROTECTED]>: > > > > > On Dec 9, 6:32 pm, jago <[EMAIL PROTECTED]> wrote: > >> No you can't. You cannot set the content-encoding in the header in > >> appengine. Even if you write your own code. Opening sockets is not > >> allowed just to remind you. > > > I'm not exactly sure what you are talking about here. You are serving > > the jars for the applet using HTTP, correct? AppEngine does not in > > *any* way restrict what output you send, other than the size. > > Umm, the documentation tends to contradict that! > > http://code.google.com/appengine/docs/webapp/responseclass.html#Disal... > > > Content- > > Encoding is just another header, and you certainly don't need sockets > > for that. Simply write a python handler that sets the content > > encoding, opens the file and writes it to the stream (stdout). > > > If you need to serve something that isn't HTTP, you're barking up the > > wrong tree. > > -- > Barry > > -www.nearby.org.uk-www.geograph.org.uk- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
