I would be happy if you could specify the versions of included third-
party libraries, e.g. ndb and webapp2.
Cheers / Fredrik
--
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@googlegroup
Hello Richard,
I had the same problem and could only resolve it by generating a new
token for the reconnecting user, i.e. calling create_channel again.
You can use the same user id though. I believe I read in the docs
somewhere that a token is only good for one sustained connection,
afterwards it'
ilable otherwise through App Engine - if you could serve it yourself,
> there'd be no need for the Channel API.
>
> What are you trying to accomplish?
>
> -Nick Johnson
>
> On Wed, Mar 23, 2011 at 4:32 AM, Westmark wrote:
>
>> Hi!
>>
>> I was just wonde
Hi!
I was just wondering how much of problem it would be to add the
possibility to serve the channel API through your own app instead of
via talkgadget.google.com. Kind of like how you serve the Remote API
by adding the handler to your app.yaml without actually writing any
code for it.
BR / Fredr
Is there any way for the client to terminate the connection while
running on the development server? I've tried calling close() and
every other function I can find on the socket and client javascript
object, but it keeps polling forever. I want to be able to kill it off
so I can setup a new connect
I totally agree. The 1MB size limit for database entities could remain
for all I care. Just give me the chance to resize my users' 5MB images
to ~300k versions. Besides, the 10MB request size limit seems out of
place when seen beside the image api size limit.
On Nov 16, 9:32 pm, Bjoern wrote:
> T