1. Using web services
in JavaScript.
Chris&an Heilmann
Fron0rends, Warsaw, Poland, October 2010

3. What is the web?

4. Was ist das Web?
Data + Interfaces

5. Lots of yummy,
yummy data.

6. If a company has a
bit of brains these
days then they build
on and release an
API for their
services.

8. Company benefits:
People bring your data and
services into environments
you could never reach.

9. Our benefits:
solve problems and get
information without buying
data or writing code.

10. Solving 2 problems.

11. Problem #1:
Distance between
two places on Earth.

12. Sometimes it would
be good to know
the distance
between two places
on Earth.

13. For this you could
use any mapping
service and
navigate from one
to the other.

14. But what if you
want to have that as
plain information?

15. Battle Plan:
1. Find the location of the two places
on Earth
2. Calculate the distance.

16. Yahoo GeoPlanet is
a data set that has
information about
the location of
places on Earth.

17. Yahoo GeoPlanet is
a data set that has
information about
the location of
places on Earth.
http://developer.yahoo.com/geo/geoplanet/

19. http://where.yahooapis.com/v1/places.q('warsaw')?
appid={appid}&format=json

20. This gives us the
latitude and
longitude of both
places...

21. ...but how do we
calculate the
distance?

22. http://www.movable-type.co.uk/scripts/latlong-
vincenty.html

23. Putting it all
together...

24. Putting it all
together...

28. Problem #1:
Foreign Tweets.

29. Twitter supports
different languages,
but has no
translation service.

30. Google has a
translation service
though.

31. Battle Plan:
1. Investigate Twitter’s search API and
Google’s translation API and if
needed, get keys.
2. Get the results from Twitter for a
certain search.
3. Loop over the results, see which
ones are not in English, and then
translate them with the Google
Translation API.

32. The solution is very
similar to the other
solution.

33. It also suffers from
the same issues.

34. Not fun with JS:
1. Asynchronous lookups with
generated script nodes are a pain to
get right - what if one breaks?
2. Depending on how many Tweets are
not in English, you have to hammer
Google’s translation API which slows
down your overall app.

35. Simplifying access.

36. Using several APIs
in conjunction in
JavaScript is not
fun.

37. It doesn’t matter if
that is internally or
externally in a
company.

38. Yahoo had a lot of
these problems...

39. ...which is why they
built YQL to work
around that.

40. Using YQL, web
services become
databases you can
access like any
other DB.

41. YQL http://developer.yahoo.com/yql/console/

42. YQL http://developer.yahoo.com/yql/console/
select {what} from {where}
where {conditions}

43. Foreign Tweets?

44. select text from twitter.search
where q=”ft2010” and
iso_language_code=”pl”

45. select * from google.translate
where q in (
select text from twitter.search
where q=”ft2010” and
iso_language_code=”pl”
) and target=”en”

46. Keywords for
Warsaw?

47. select * from search.web
where query="warsaw"

48. select abstract from
search.web where
query="warsaw"

49. select abstract from
search.web(100) where
query="warsaw"

50. select * from
search.termextract where
context in (
select abstract from
search.web(100) where
query="warsaw"
)

51. select * from
search.termextract where
context in (
select abstract from
search.web(100) where
query="warsaw"
)
| sort(field="Result")
| unique(field="Result")

52. Photos of Warsaw?

53. select * from
flickr.photos.search(50) where
woe_id in (select woeid from
geo.places where
text="warsaw") and
min_taken_date = "2009"

54. Instead of going
crazy filtering and
sorting in JS...

55. ...use the YQL server
and then have a very
simple JS for
displaying.

56. Using web services
with YQL in JS.

57. YQL is a web
service endpoint on
its own...

58. https://query.yahooapis.com/v1/public/
yql?q={uri-encoded-query}&
format={xml|json}&
diagnostics={true|false}&
callback={function}&
env=store%3A%2F%2Fdatatables.org
%2Falltableswithkeys

59. As it supports
JSON-P you can use
it with dynamically
created script
nodes.

61. Special case:
Scraping
http://www.flickr.com/photos/fdtate/4426760544/

62. http://www.slideshare.net/cheilmann/reasons-to-be-cheerful-fronteers-2010

64. select * from html where
url="http://www.slideshare.net/
cheilmann/reasons-to-be-cheerful-
fronteers-2010"
and
xpath="//ol/li/p[contains(.,'http')]"

65. http://y.ahoo.it/r/ENSPGm

66. http://lanyrd.com/people/codepo8/

67. HTML as JSON is
not fun.

68. JSON-P-X =
HTML as a string in
a JSON-P container!

70. Using YQL re-use of
web content is very
easy indeed.

71. Be safe,
be good...

72. Using JSON-P in
JavaScript is easy.

73. Don’t rely on
data arriving -
test for it!

74. XML to JSON?

75. XML to JSON?

76. Using JSON is easy
with libraries.

77. JSON-P and jQuery:
$.getJSON(url+'&callback=?',
function(data){
});

78. JSON-P and jQuery:
$.ajax({
url: url,
dataType: 'jsonp',
jsonp: 'callback',
jsonpCallback: 'ohyeah'
});
function ohyeah(data){
}

79. Which one to use?

80. getJSON() is
dangerous with
other people’s data.

81. $.ajax():
http://{...}&
format=json&callback=ohyeah
$.getJSON():
http://{...}&
format=json&callback=jsonp1282497813335
Random number

82. Cachebreaking is
not a good idea.

83. Local caching is a
good idea though.

84. Cookies
suck,
though.

85. Would be good to
have a better
solution for that.

86. localStorage =
cookies on steroids.

87. if(('localStorage' in window) &&
window['localStorage'] !== null){
localStorage.setItem(
'cake',
'much better than cookies'
)
}

88. if(('localStorage' in window) &&
window['localStorage'] !== null){
var what = localStorage.getItem(
'cake'
)
// what -> 'much better than
cookies'
}

89. localStorage only
stores Strings - use
JSON to work
around that.

90. if(('localStorage' in window) &&
window['localStorage'] !== null){
localStorage.setItem(
'cake',
JSON.stringify(
{yummy:‘yes’,candles:5}
)
);
}

91. if(('localStorage' in window) &&
window['localStorage'] !== null){
var what = JSON.parse(
localStorage.getItem('cake')
);
// what -> Object{...}
// and not [Object object]
}

92. Let’s wrap this up in
a function.

93. yql - the query
id - storage key name
cacheage - how long to cache
callback - obvious, isn’t it?

94. Browsers
supporting
localStorage fetch
the data every hour.

95. Others still work,
but load the data
every time.

96. OK, dann machen
wir das halt..

97. OK, dann machen
wir das halt..

98. OK, dann machen
wir das halt..

106. There are a few
libraries offering
fallbacks to other
browers via Flash.

107. You can of course
also use those.

108. Offering your own
API.

109. To get your own API
into YQL all you
need to do is write
an XML schema and
put it on GitHub.

110. http://github.com/yql/yql-tables

111. YQL allows you to
write “executable
tables”...

112. ...which means you
can convert data
with JavaScript that
will be executed
server-side.

113. Twitter translate
example:

114. Offering your own
API.

115. Offering your own
API.

117. SELECT * FROM
twitter.translate WHERE
language="en" and
search="warsaw" and
amount="20"

118. Distance example:

121. SELECT * FROM geo.distance
WHERE place1=”london” and
place2="warsaw"

122. http://isithackday.com/hacks/geo/distance/

123. Using your JS
tables.

124. Write your schema,
put it on the web
and use, err... USE
to, err... use it.

125. use “http://app.pl/distance.xml”
as distance;
SELECT * FROM distance
WHERE place1=”london” and
place2="warsaw"

126. Both
problems
solved
and
released
as an API
- in JS!

127. In summary
Use YQL instead of wasting time
reading API docs for a simple task
Filter data in the service and get the
info back in formats you need.
Use the fast YQL server instead of
doing lots of requests.
Write your own JS APIs using
execute.
Use local storage and don’t break
caching.
Go and use the web.

128. Christian Heilmann
http://wait-till-i.com Cheers
http://developer-evangelism.com
@codepo8