XMLHttpRequest which is constrained by the Same Origin Policy. Therefore, I reverted to JsonRequest that supports safe cross-site communication. Luckly, Geonames supports JSON web service requests.function processLocation1(jData){
if (jData == null) {
// There was a problem parsing search results
alert("Error parsing geoname data");
return;
}
locationData = 'just arrived close to ' + jData.geonames[0].name + ' in ' + jData.geonames[0].adminName1 + ', ' + jData.geonames[0].countryName;
}
function geonameRequest(request){
// Create a new script object
aObj = new JSONscriptRequest(request);
// Build the script tag
aObj.buildScriptTag();
// Execute (add) the script tag
aObj.addScriptTag();
}
function reverseGeonameLookup(){
var request1 = 'http://ws.geonames.org/findNearbyPlaceNameJSON?lat=' + lat + '&lng=' + lng + '&callback=processLocation1';
geonameRequest(request1);
}
function showMap(position) {
lat = position.coords.latitude;
lng = position.coords.longitude;
}
function getLocation() {
if (navigator.geolocation) {
navigator.geolocation.getCurrentPosition(showMap);
} else {
error('not supported');
}
}
The showMap(position) is a callback function used as soon as the browser identifies your location. Please note that this approach is currently known to work in Chrome, Firefox and Safari for mobile (e.g. Ipad and Iphone). It seems that other browsers will support geolocalization in the near future.<script type="text/javascript" src="http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.2">This will show yourself in a BingMap, in this particular case I used the pretty cool Birdseye style.
<script type="text/javascript">
var map = null; // the map object
var lat = null; // latitude
var lng = null; // longitude
var locationData = null; // string msg
function showMap(position) {
lat = position.coords.latitude;
lng = position.coords.longitude;
// load map
map = new VEMap('myMap');
map.LoadMap(new VELatLong(lat, lng, 0, VEAltitudeMode.RelativeToGround), 16,
VEMapStyle.Birdseye, false, VEMapMode.Mode2D, true, 1);
}
<script type="text/javascript">
window.fbAsyncInit = function() {
FB.init({appId: '117083285001944', status: true, cookie: true,
xfbml: true});
};
(function() {
var e = document.createElement('script');
e.type = 'text/javascript';
e.src = document.location.protocol +
'//connect.facebook.net/en_US/all.js';
e.async = true;
document.getElementById('fb-root').appendChild(e);
}());
function streamPublish(name, description, caption, hrefTitle, hrefLink, userPrompt, thumb, urlThumb){
FB.ui(
{
method: 'stream.publish',
message: '',
attachment: {
name: name,
caption: (caption),
description: (description),
href: hrefLink,
media: [{ type: 'image', src: (thumb), href: (urlThumb)}]
},
action_links: [
{ text: hrefTitle, href: hrefLink }
],
user_prompt_message: userPrompt
},
function(response) {
});
}
</script>
A new generation of low-cost, high-performance database software is rapidly emerging to challenge SQL's dominance in distributed processing and Big Data applications. Some companies have already traded SQL's rich functionality for these new options that let them create, work with, and manage large data sets.
A big reason for this movement, dubbed NoSQL, is that different implementations of Web, enterprise, and cloud computing applications have different requirements of their databases. Not every app requires rigid data consistency, for example.
Posts
All Comments
