What's in this Guide?
- Basic Tutorial - Continue with a basic example of a web page that uses the Gigya service - a basic Facebook app, and a guide for using Gigya Web SDK methods.
- Events - Learn how to handle Events generated by Gigya socialize.
- Advanced Customizations - Advanced customization options that you may apply on your client application.
- Supported Browsers - Information about Gigya's browser support.
An Asynchronous Programming Model
Gigya uses an asynchronous programming model in which operations are triggered and then run in the background until they are completed. Upon successful or unsuccessful completion, the operation invokes a callback function, which is provided by the developer, and returns a response object that includes the results of the operation. The callback function should handle the response in an appropriate manner, as determined by the application.
The SDK Namespaces
The entire range of Gigya functionality is provided as methods of one of the following namespaces: gigya.socialize, gigya.accounts, gigya.comments, gigya.gm and gigya.ds, thus all methods are referenced with the gigya. prefix.
Loading The Gigya Web SDK
The first thing you need to do is ensure that you have our Web SDK loaded on every page of your site that you will be using Gigya services. This is accomplished by sourcing the SDK from our CDN in the <head> of all your pages. To do this, simply add the following code to your sites header template.
Where, depending upon your site's protocol, <Site_Protocol_and_CDN_Prefix> is:
- - Site uses SSL
- - Site does not use SSL
us1.gigya.com- For the US data center.
eu1- For the European data center.
au1- For the Australian data center.
ru1- For the Russian data center.
cn1- For the Chinese data center.
If you are not sure of your site's data center, see Finding Your Data Center.
Calling The Method
All the methods in the Gigya Web SDK have a common signature:
The "params" object is actually an object that may contain multiple members. We choose to use this object instead of passing parameters in the "classical" way - this provides flexibility in adding new parameters without "breaking" older code.