[google-appengine] Re: 1.6.1 Pre-release SDKs are live
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@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel use/reuse question
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's discarded. BR // Fredrik On May 12, 1:57 pm, Richard Arrano rickarr...@gmail.com wrote: Hello, I've been using the Channel API and for each chat room, I have a fixed number of users. So for each room, prior to the launch, I call create_channel for each user and store it in a dictionary that I save in a TextProperty. When I want to broadcast, I read the TextProperty and convert it back to a dictionary, then call channel.send_message on each. This works well initially. However, when a user exits the session and comes back, it invariably causes this error each time: File C:\Program Files\Google\google_appengine\google\appengine\api \channel\channel_service_stub.py, line 127, in _Dynamic_SendChannelMessage self._channel_messages[client_id].append(request.message()) KeyError: '21024-21026-185804764220139124118' Where the first two numbers are some identifiers and the last part is the user id. Does something get used up so to speak when the client opens the initial connection? I've seen people suggesting reusing tokens instead of calling create_channel each time, which is what I'm trying to do. Does anyone have any ideas why this would occur? Thanks, Richard -- 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 google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Serving talkgadet.google.com through your own app
Ok, I see. My devious plan is to circumvent all the webfilters out there which are already blocking talkgadget.google.com due to Google Talk. I have several friends stuck behind such filters and they want to be able to use all the features on my site. So I was hoping that my domain could act as a proxy in front of talkgadget.google.com so the filter does not block it. BR // Fredrik On Wed, Mar 23, 2011 at 5:48 AM, Nick Johnson (Google) nick.john...@google.com wrote: Hi Fredrik, This isn't possible - the Channel API provides a service that isn't available 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 fredrik.westm...@gmail.comwrote: 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 / 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@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Nick Johnson, Developer Programs Engineer, App Engine -- 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 google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Serving talkgadet.google.com through your own app
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 / 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@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel API future improvements?
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 connection with a fresh token without the browser going nuts with requests. BR // Fredrik On 7 Feb, 18:15, Tim meer...@gmail.com wrote: On Monday, February 7, 2011 5:05:06 PM UTC, Peter Petrov wrote: You can change the dev-server polling interval in your JavaScript code quite easily. For example: goog.appengine.Socket.POLLING_TIMEOUT_MS = 5000; // 5 seconds Ah, so you can... and here was me looking for ways to get hold of the goog.Timer objects or similar. And changing that value on the fly changes the timeout for the next call (ie it's not something you can only change before creating a channel) - thanks... I feel quite foolish now :) -- T -- 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 google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Limit on image size very low
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 bjoer...@googlemail.com wrote: The latter - it throws an error if the image you try to manipulate is bigger than 1MB in memory. On Nov 16, 8:03 pm, Eli Jones eli.jo...@gmail.com wrote: I haven't used the Image api.. but.. do you mean the limit of 1MB for storing entities in the Datastore? Or, does it just throw errors if you try to manipulate an image in memory that is over 1MB? If you're just trying to get a 1MB image into the datastore, you could break it up into 1mb chunks before sticking it in the datastore. -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=.
