Slides from the talk that I did on the 4th December 2009 at Apache Con Asia '09.

1. Apache Shindig, from Server Side Portlets to Open Social Gadgets Tyrell Perera (Product Manager WSO2 Gadget Server and WSO2 Mashup Server) & Nuwan Bandara (Software Engineer, WSO2 Gadget Server)

3. The Google Gadgets Specification

4. Apache Shindig

5. A Case Study

6. The Role of Portals in Today's Service Oriented World

8. pluggable,

10. functionality

14. They are self-contained, which means they should not be modified

15. Individually, they may or may not have a presentation layer

16. But the end users need a unified view to make use of all this!

19. environment for proper functioning of the components plugged into it

21. Independent of programming languages or platforms

26. PHP

27. .Net

29. to provide a single unified view to the end user

33. In essence, a Portlet's output finally reaches the user as HTML, Javascript or any browser friendly medium

35. The Portal only needs to know this URL and nothing else?

37. The Google Gadgets Specification

39. They allow developers to easily write useful web applications that work anywhere on the web without modification

42. The container is responsible for managing the gadgets' layout and controls,

44. Passing the user's locale (for i18n)

45. Storing user preferences

46. Authentication ...

48. The <Module> tag indicates that this XML file contains a gadget

49. The <ModulePrefs> tag contains information about the gadget such as its title, description, author, and other optional features

50. The line <Content type=&quot;html&quot;> indicates that the gadget's content type is HTML

51. <![CDATA[ ...insert HTML here... ]]> is used to enclose HTML when a gadget's content type is html. It tells the gadget parser that the text within the CDATA section should not be treated as XML. The CDATA section typically contains HTML and JavaScript

52. </Content> signifies the end of the Content section

53. </Module> signifies the end of the gadget definition

54. In a nutshell ...

55. A Typical Gadget Based Portal iGoogle, Orkut, Hi5

60. The OpenSocial Specification

61. Status Source: https://www.ohloh.net/p/10942/analyses/latest

63. hi5

64. Partuza, based on PHP Apache Shindig

65. WSO2 Gadget Server, based on Java Apache Shindig

66. etc.,

69. OpenSocial Data Server

70. Gadget Rendering Metadata Translate Prefs Features

71. Source: http://chrisschalk.com/shindig_docs/rajdeep/shindig-overview/onjava-shindig-overview-tidy.html

72. Our Experience With Apache Shindig

74. The result...

77. The gadget preferences were loaded asynchronously

82. Open Social http://code.google.com/apis/opensocial/

83. Gadgets Developer Reference http://code.google.com/apis/gadgets/docs/dev_guide.html

84. Apache Shindig Project Page http://incubator.apache.org/shindig/

85. WSO2 Gadget Server Project Page http://wso2.org/projects/gadget-server

86. Q&A