Obsolete
Status Update
Comments
si...@google.com <si...@google.com>
la...@gmail.com <la...@gmail.com> #2
We are planning a very cool implementation shortly using google maps and having these
icons clickable on our map would be a huge bonus to mass transit users. The best way
for this to work would be to be to have some way to capture the data in order to
integrate it into our own maps but I would be happy even if they were just clickable
and displayed exactly as they do atmaps.google.com .
icons clickable on our map would be a huge bonus to mass transit users. The best way
for this to work would be to be to have some way to capture the data in order to
integrate it into our own maps but I would be happy even if they were just clickable
and displayed exactly as they do at
si...@google.com <si...@google.com> #3
Since you labeled this ApiType-Javascript, does that mean we Flash API users
shouldn't expect support for transit?
shouldn't expect support for transit?
[Deleted User] <[Deleted User]> #4
This was originally requested for the JS API. If you're a Flash user interested in
the same functionality, please file a new feature request. Thanks!
the same functionality, please file a new feature request. Thanks!
la...@gmail.com <la...@gmail.com> #5
I too would love to see this feature as a selectable layer based on API calls.
la...@gmail.com <la...@gmail.com> #6
Being able to get the public transit information through the API would be very cool
and useful!
Regards,
Badih Schoueri
zipalong.com
and useful!
Regards,
Badih Schoueri
la...@gmail.com <la...@gmail.com> #7
Changing status of "Accepted" issues to "Acknowledged", to clarify their
state.
We may not be able to resolve all bugs or fulfill all feature requests, but
we do thank you for filing them, and we will continually revisit all
acknowledged issues and evaluate their feasibility. Thanks!
state.
We may not be able to resolve all bugs or fulfill all feature requests, but
we do thank you for filing them, and we will continually revisit all
acknowledged issues and evaluate their feasibility. Thanks!
tr...@gmail.com <tr...@gmail.com> #9
what are the developments on this request ? any time tables ?
Many thanks,
Many thanks,
jo...@gmail.com <jo...@gmail.com> #10
is there a new update?
jo...@gmail.com <jo...@gmail.com> #11
++
jo...@google.com <jo...@google.com>
[Deleted User] <[Deleted User]> #13
This would be a great enhancement
pt...@google.com <pt...@google.com> #14
Is this feature now available in v3? I notice the icons in there, but not clickable for information?
Description
There's a separate issue for improving startup time, also a worthy goal:
This issue is about fixing the failure mode when GAE gets sick. A 100+ second startup time is painful. User-facing downtime because we can't get any instances running is deadly. If a 'normal' startup is 20s, and a 'deadly' startup is 60s, there's a safety margin of 3X. However, observed variance in startup times exceeds this 3s.
Yes, GAE shouldn't get sick and have spikes in startup time. But just as importantly, it should have a 'graceful' failure mode in the rare case that it does. One solution is that startup requests should be allowed to run more than 60s - the safety margin should be more than 3X.