Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We've submitted online form https://developers.google.com/maps/ios-access back in Dec 2012 however we still have not received any response from Google.
Does anyone who posted similar request back in Dec know how long does it regularly take Google to reply to such requests?
If we know it, it will help us (and maybe others who posted similar questions) to plan on when we can start development of our iPhone app because
Unfortunately, self-service method for API key generation through API Console suggested at "Obtaining an API Key" section of https://developers.google.com/maps/documentation/ios/start does not work for us as we simply do not see "Google Maps SDK for iOS" in services list.
Also as of our verification (unless we did it in wrong way), SDK does not work without API key.
I applied for access on the 13th of December, and then received an email saying I'd been approved on the 17th of December.
But I don't think this should be taken to mean that it takes 4 days to get approved.
Google are rolling out access to their SDK gradually. They may have received way more requests than they want to provide access to yet. Maybe they've already reached an initial quota, and are waiting for something (like releasing a new version, or optimizing their back end, etc) before releasing any more. Or maybe they are releasing them in batches of N per day or something. So it may take some time before anyone else gets approved.
Also I'm not sure if Google is releasing them on a first-come, first-served basis. The request form asks if you have an existing app on the app store. Maybe Google are releasing access based on if you have an app, and if you do, how popular it seems and/or how integral maps are to the app, or something like that.
So at this stage, I think all you can do is wait.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 13 days ago.
This post was edited and submitted for review 12 days ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
I have a full stack app that uses React, Node.js, Express, and MySQL. I want the react app to respond to database updates similar to Firebase: When data changes, I want a real-time notification sent to my app.
I want to use stock MySQL (no plugins), so that I can use AWS RDB or whatever.
I will use socket.io to push the real-time notifications to the web app.
To avoid off-target responses, I'll summarize various approaches that are not what I am looking for:
The server could poll, or each client could poll. (Not real-time, but included for completeness. When I search, polling is the only solution I find.)
Write a wrapper that handles all MySQL updates, handles subscriptions, and sends the notifications. This is a complicated component that adds complexity. Firebase is popular because it both increases performance and reduces complexity. I like Firebase a lot but want to do the same thing with MySQL.
Use Firebase to handle the real-time notifications. The MySQL wrapper could use Firebase to handle the subscriptions and notifications, but there is still the problem of triggering the notifications in the first place. Also, I don't want to use Firebase. (For example, my application needs to run in an air-gapped environment.)
The question: Using a stock MySQL database, when a table changes, can a notification server discover the change in real-time (no polling), so that it can send notifications?
To clarify: by "stock MySQL", I mean no plugins, no need for C compilers, and even no need for root access.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm programming a software based on google maps api for emergency vehicles. Is it possible to make the directions api allow breaking traffic rules (like turning left where it's not allowed)?
Thank you
I don't think it is still possible with the latest version of Maps API. It is still a feature request.
Also, I don't see if a workaround exists.
I'm afraid there is even worse thing that might disallow using of Google Maps API in applications for emergency vehicles.
Have a look at paragraph 10.2 (g) of Terms of Service. It reads:
General Google API Restrictions. The following restrictions apply generally to all Google Services, including the Google application programming interfaces at https://developers.google.com/products/ (or such other URL as Google may provide) (the “Google API(s)”). You will not:
g. Use the Google APIs for any activities where the use or failure of the Google APIs could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems).
https://developers.google.com/maps/terms?#section_10_2
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Instead of the the location presented is based on the user I want it to update automatically based on where I am.
I could obviously hard-code it but I want it to be automated. I travel quite a bit: when I am in Egypt I want it to say something like "working in Egypt" or when I am home in NYC "working at homebase" etc.
I am not sure how to go about this, I am assuming it can be done with HTML5 and some more but I may be wrong any suggestions welcome.
There are a lot of ways, but they all have in common you have to send your location to somewhere, and that somewhere has to inform that location to your website visitors (or the place where you want to display it).
You can use HTML5 location api to determine your approximate location. For example, you set up a page (not the index page, but one you can authenticate to) that whenever you visit it, you inform your location to it. That's done with a simple
navigator.geolocation.getCurrentPosition(function (location) {
console.log(location);
});
For the second step, you have several ways to go:
Use a backend server to persist that data in somewhere that's not just your notebook. That server can, in turn, store that location in a Database. Then, anyone visiting your website public page could see from where did you updated your location the last time.
Instead of Databases, you can also use websockets to just relay your updates to whomever is visiting your website at a given moment. But that might be just too far fetched for what you need to do.
Use a webservice API to inform others about your location. Automated foursquare checkins? Tweets, Facebook statuses? All of those approaches is unique to the given API, but most social networks allow you to build simple apps to do that.
TL / DR
Yes, you can use HTML5 to guess your approximate location. Nope, with HTML5 alone you can't tell other people where you are.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have a #mydomain.com and via Gmail Google Apps for business. It was down for 2 days so I did not receive emails that bounced from clients. Is there anyway to get those messages now that the email is back up?
The answer to this would completely depend on why the emails were bounced.
For example, if your MX records weren't pointing to Google's servers, no, this wouldn't be possible in Apps as the messages never hit Google's servers to begin with. You will need to reach out to any clients that you suspect received bounce messages and ask them to resend them.
Some DNS providers also offer email spooling services in the event of some DNS setting causing failures to deliver messages, etc. You would need to contact them to check on this though.
If the mails were making it to Google's servers but Apps was bouncing them for some reason, you can check the Email search log to find the bounced messages.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
In my 4 years of experience,I have developed a lot of web applications. Now, the concept of programmable web getting more and more popular, new APIs are being released almost everyday. I would like to develop a java API/library for a few of these endpoints.Ex stackapps,reddit,digg etc... What I would like to know from you people is ,
How is the API of the regular web
apps differ from the API of these
libraries. Or what is the difference
between these two from design
perspective
What are the best API development
practices.
What are all the factors that I need to consider before designing the API
.
Please comment, if the details are not sufficient.
Stability
If you offer an API to your web app, it is probably because you want other people to build applications using it. If it is not stable they will hate you for forcing them to follow through your frequent changes. If this takes too long, their site might remain non-functional for a long time while they are figuring out the new way of doing things in your API.
Compactness
You want the API to be complete but compact, as in not too much to remember.
Orthogonality
Design it so there is one and only one way to change each property or trigger an action. Actions in an orthogonal API should have minimal (if ever) side effects.
Also, it's not a good practice to remove a feature from a public API once released.
Security and Authentication
Since the API is web-exposed, you will have to authenticate each request and grant appropriate access. Security common sense applies here.
Fast Responses or Break into pieces
I believe in a web environment we should have fast responses and avoid requests that will take too long to complete. If it's unavoidable then it is better to send an ACK and break the task into several pieces and subsequent calls.
From my experience, all good API were not made to solve a generic problem, but to solve a problem for some that requires a certain abstraction. This abstraction is then evolving as the requirement and/or the underlying layer change.
So instead of finding the API that will do it all, I'd start by finding one or two good case problem were your API could help.