Hi Malaka,

Thanks for your valuable thoughts. We'll go with the approach you mentioned.

Regards !


On Wed, Feb 12, 2014 at 2:08 PM, Malaka Silva <[email protected]> wrote:

> Hi Chanaka,
>
> Please find following comments.
>
> On Wed, Feb 12, 2014 at 12:59 PM, Chanaka Dharmarathna <
> [email protected]> wrote:
>
>> Hi Malaka,
>>
>>
>> On Wed, Feb 12, 2014 at 11:42 AM, Malaka Silva <[email protected]> wrote:
>>
>>> Hi Chanaka,
>>>
>>> With different versions can we use the same set of input parameters?
>>>
>>
>> It can be changed. However we cannot guarantee on this since all the
>> rights have the API owner.
>>
>     Write the connector for widely used version
>
>>
>>
>>> If there are specific parameters for specific version we need to
>>> hardcode it and do different versions of the connector accordingly.
>>>
>>
>> I agree to this. But when considering the situation pointed by Indika,
>> how we support that ?
>> 1. Parameterize URL without version (*{uri.var.apiUrl}*/v1/people/~).
>> Here we can set default value of uri.var.apiUrl to "
>> https://api.linkedin.com";
>>  2. Hard code complete URL (https://api.linkedin.com/v1/people/~). We
>> can use mostly used API URL for this (https://api.linkedin.com).
>>
>    Give the URL as an optional parameter. Set the default to    "
> https://api.linkedin.com";
>
>>
>> Regards !
>>
>>
>>>
>>> Best Regards,
>>> Malaka
>>>
>>>
>>> On Wed, Feb 12, 2014 at 12:30 AM, indika prasad <[email protected]>wrote:
>>>
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-Use-API-URL-as-Parameter-for-Connectors-tp92062p92064.html
>>>> Sent from the WSO2 Development mailing list archive at Nabble.com.
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/>
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Chanaka Dharmarathna
>> *http://chanakaindrajith.blogspot.com/*<http://chanakaindrajith.blogspot.com/>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/>
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Chanaka Dharmarathna
*http://chanakaindrajith.blogspot.com/*<http://chanakaindrajith.blogspot.com/>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to