Are you still having trouble retrieving messages? The problem with presence
has been fixed since about 2am this morning, but I haven't heard any other
reports of dropped messages, and I'm not able to reproduce that.
On Mon, Apr 2, 2012 at 8:08 AM, Aleksei Rovenski aleksei.roven...@gmail.com
Please fill out this spreadsheet and we'll up the mail quota for your app:
https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dENESzEwNzJiZEdpQkRzTl9RNElVWUE6MQ#gid=0
On Monday, March 19, 2012 2:14:13 PM UTC-6, PK wrote:
+1 I never got an answer on this one and would like to
Can you tell me your appids? I can take a look.
On Mon Mar 12 03:03:59 GMT-700 2012, Alexis alexis.hanico...@gmail.com
wrote:
Similar issue for us,
for one of our apps it works fine, for one other, our test and stage apps
works correctly but once in production mails are not delivered, or
with mail deliverability, or you have
other questions, please contact us at http://goo.gl/ldsGA
Thanks-
-Moishe Lettvin
Mail API Tech Lead
--
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
On Feb 21, 12:30 pm, Joshua Smith joshuaesm...@charter.net wrote:
The case that matters is when the server is sending an administrative email,
and we'd like the headers there to reduce the probability of those emails
being tagged as spam.
In most cases, nobody at all will be signed in. These
We made a change recently so that applications do not receive
unlimited recipient quota until they have successfully cleared a
charge (previously unlimited quota was granted when billing was
enabled). So if your app is in the approximately 7-day window between
enabling billing and clearing a
will stay as
minutes requested rather than minutes consumed for the foreseeable
future.
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine
This should be resolved now; it was related to the new channel_minutes
quota. Please post if you see any more problems with this.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
the JIDs (offline, my
email is moishel at google.com) if it's a consistent set of JIDs?
Thanks!
-Moishe
On Nov 8, 12:13 pm, Gerald Tan woefulwab...@gmail.com wrote:
According
tohttp://code.google.com/appengine/docs/java/javadoc/com/google/appengi...
XMPPService.getPresence is deprecated.
Fair
Do you have any details on what the server response to the script
request is for these?
A workaround might be directly requesting http[s]://
talkgadget.google.com/talkgadget/channel.js (the request to /_ah/
channel/jsapi redirects to this path)
I'll investigate.
--
You received this message
. There is a feature request on our
issue tracker (http://code.google.com/p/googleappengine/issues/detail?
id=4764) to move these off of the talkgadget domain.
Hope that sheds some light-
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App Engine group
ETA is about 2 hours for complete rollout of fix.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/LmmXiuBBFh0J.
To post to this group, send email to
On Jul 27, 12:51 pm, Ice13ill andrei.fifi...@gmail.com wrote:
Even though it is the same channel, when i call the create method
(let's say i hit refresh on my browser, and the channel is created at
page load) my Channel Api quota for created channels rises...
That's correct, because you're
the datastore with a memcache layer on top in apps I've written.
You could have eg. a table of user_ids (from the users API)
representing connected users.
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group
I took a brief look at your application and noticed an exception gets
thrown after registration. If I go directly through the sign-in page
things seem to work. Maybe that exception is causing code to stop
working so open doesn't get called?
--
You received this message because you are subscribed
Disconnect notifications could arrive up to a few minutes after the
browser window's closed -- usually the browser is good at telling us
the client's gone, but sometimes it isn't and we have to wait for a
lack of heartbeats to tell us the client's gone.
On Jul 4, 1:41 am, Amorgos
Sending Channel messages is asynchronous in that the function's return
is not gated on the client receiving the message. Internally, though,
the call waits for a response to an RPC so the time to call
sendMessage can take on the order of 10s of milliseconds; if you're
sending tons of messages it
was finally working.
Moishe, thanks for your help :)
Kind regards,
Z
On Thu, Jun 16, 2011 at 5:18 PM, Zerot Samsa zerotsa...@gmail.com wrote:
Well...
i've tried simplyfing the channelId, but that didn't solve the problem
So we migrated to version 1.5.0.
As a result we now do
First, what version of the SDK are you using? It looks like you're
using something before 1.5.0 (based on the text of the error message)
-- can you try with 1.5.0?
Basically the logic that's happening here is:
- the application calls create channel
- the dev appserver gins up a token
That token looks malformed to me. The dev appserver tokens shouldn't
have an @ in them. Is that the value directly returned by
ChannelService.createChannel() or is it modified in some way?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
Are you all using GWT?
Any chance you can include some debug logs that include a request to /
_ah/channel/dev/.*? And also log the token that's returned from
ChannelService.CreateChannel?
Thanks-
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App
That exception happens when a javascript page is left running between
re-starting the dev appserver. You can get around it by closing the
client page when you re-start the dev appserver.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
Hi, Matthew - the only thing I can think of before digging into the
logs is that your appid + channelkey combo might be too long.
If you tell me your appid, I can look at the logs and see if something
else is going wrong.
Thanks!
-Moishe
--
You received this message because you are subscribed
Okay, I've repro'd this problem. It looks like this occurs when you
have a high-replication datastore app (which all new apps are, by
default, now) and are using the non-default version. Working on a fix
now; in the meantime, using the default version of your app should
work.
Thanks-
-Moishe
(in the 'else' clause of 'if client_id
in self._connected_channels' in connect_channel)
244 self._connected_channels.append(client_id)
self._channel_messages[client_id] = []
Hope that helps-
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App
created, or the cross-frame communication we're using to relay
messages from that iframe out to the host is getting broken somehow.
Thanks!
-Moishe
--
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
Hi, Ronald. I'm looking into this today, will try to get back to you
later on with some more information.
Is this only happening with Chrome extensions? Which channel of Chrome
are you running - dev, beta or main?
Thanks!
-Moishe
--
You received this message because you are subscribed
Okay, I've identified and fixed the problem, and am working on getting
a fix rolled out to production. No ETA on that yet.
In the meantime if you'd like a patched jsapi file that you can serve
statically from your own site, contact me directly at moishel at
google.com.
--
You received this
There's a fix for this rolling out soon (should be within a week).
In the meantime, you can copy the file locally and serve it statically
from your app (with the correct mime type). I realize that's not an
ideal solution, but it should work.
On Mar 21, 8:34 pm, Navraj S. Chohan nlak...@gmail.com
Is this just on the dev appserver? There is a known bug that the
encoding isn't set properly that'll be fixed in 1.4.3.
--
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.
of flushing the queue in
production) No firm ETA on this yet but it's in the pipeline.
In response to Will's question about opening a channel, navigating
away, then returning to the page: in production, any messages sent
when the client's not connected to receive them will be dropped.
-Moishe
socket.close() in this case instead of messing with the DOM
directly)
Hope that helps!
-Moishe
--
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
I've seen that error (on line 80) when the token that's passed to the
goog.appengine.Channel constructor is malformed -- either with extra
stuff (eg. a carriage return) or not the value returned by
create_channel. The next release of the channel.js, in a couple of
weeks, will include more
Hi there - there's a known issue where socket.close() doesn't work. A
fix for that should make it to production in the next week or so.
In the meantime, you can manually delete the iframe named 'wcs-iframe'
from your page. Sorry for the inconvenience.
-Moishe
On Jan 13, 2:58 am, Will Vincent
On Jan 10, 1:29 am, Flori floon...@googlemail.com wrote:
Hi Moishe,
little reminder ;) could you take a look over?
Sorry about that, got distracted by the holidays :) Taking a look
now...
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
thrown when this
happens.
Thanks!
-Moishe
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java
will be able to register a handler to indicate that the
channel is fully open, without needing to write custom client code)
I'll see if I can repro number 2; I haven't heard this before. If you
try to manually re-open with the same token, does that work?
Thanks!
-Moishe
--
You received
Publishing the uncompiled files is in the works! I know it'll be useful for
those of you using closure (it could save a lot of code size). No definite
time line but I'm working on it now.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To
Yep, connect/disconnect is in the works. No firm ETA, but it's coming.
--
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
I think this was also asked/answered over in the python group, but I'll post
here too for the sake of completeness:
1. Token expires two hours from when you call create_channel. So if you
wanted to store it server side, you could also store a time stamp. Note that
the expiration's accuracy is
Assuming that a channel setup costs 2.77 seconds, having just 10,000 active
users setup 4 channels per day would cost $92.30 per month. That's not
counting any CPU costs for actually sending messages.
At that rate, I can't really use the channel API as much as I'd like and I
have to look
Hi, Will - thanks for the feedback.
This is an artifact of how the dev appserver works (because of
polling, we need to queue messages), but the Channel API doesn't
behave this way in production.
--
You received this message because you are subscribed to the Google Groups
Google App Engine
.
-Moishe
--
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
On Dec 4, 8:22 am, Austin aus...@gmail.com wrote:
You could reuse a token for a particular user within the token's two
hour window.
Yes, I was going to suggest something like this. You can store the
token and the time it was created in a cookie, and re-use the token if
it hasn't expired.
If
Latency should be generally significantly less than 500ms (that's not
a guarantee, but it's what I've been seeing in my end-to-end tests).
Channel set-up time (the time between when you call
goog.appengine.Channel.open and when your socket.onopen callback gets
called) can be longer, sometimes up
; if there are scenarios that you think need this
kind of multiplexing though please let me know.
Thanks for your questions!
-Moishe
--
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
46 matches
Mail list logo
