Hi Chanaka, Some API like linkedin has given few options for their api url. As an example, linkedin api can be either any of below urls for get user detial operation.
01. http://api.linkedin.com/v1/people/~ 02. https://api.linkedin.com/v1/people/~ 03. http://www.linkedin.com/v1/people/~ 04. https://www.linkedin.com/v1/people/~ IMO is basically its user call to select the best fitting URL. WDYT? Thanks BR Indika Kularathne On Tue, Feb 11, 2014 at 11:39 PM, Chanaka Dharmarathna < [email protected]> wrote: > Hi, > > I'm developing LinkedIn connector supporting to their REST API [0] and > having some doubts on parameterizing the LinkedIn API URL (including the > API version - > http://api.linkedin.com/v1/<http://developer.linkedin.com/documents/profile-api#> > ). > > I figured out 3 ways. > > 1. Let the user send the API URL with version. Here user can chose which > API version to use. > 2. Set default API URL with version inside the init method. This way, it's > not essential to pass this parameter, but still user can override. > 3. Without parameterizing API URL, hard code it inside the synapse > template. > > What is the most suitable approach out of those 3 options ? > Or else is there any other suited option ? > > Any thoughts on this would be highly appreciated. > > [0] : http://developer.linkedin.com/rest > > Regards ! > -- > Chanaka Dharmarathna > *http://chanakaindrajith.blogspot.com/*<http://chanakaindrajith.blogspot.com/> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
