Feedback on ExternalResourceClient vs Guzzle

Hi Sugar Devs,

We'd like to collect some feedback on our Sugar ExternalResourceClient over Guzzle.

Are there functions or functionality that you use in Guzzle that aren't available in ExternalResourceClient?

Could you provide us with some examples that we can use to improve ERC?

Thank you very much,

Rafael Fernandes

Parents
  • Hello Rafael,

    The main issue we encountered is linked to the validation of licences of SugarOutfitters using ExternalResssourceClient.

    Before making a API call to a URL, ERC translates the domain name into an IP adress. This poses issues when there are multiple IP adresses behind a domain name making the management of proxy/firewall more difficult and sometimes impossible (on some entry-level solutions). 

    Besides this, all other issues we encountered have been adressed by the Sugar team.

    Kind regards,

    Vlad TANASOIU / Synolia

Reply
  • Hello Rafael,

    The main issue we encountered is linked to the validation of licences of SugarOutfitters using ExternalResssourceClient.

    Before making a API call to a URL, ERC translates the domain name into an IP adress. This poses issues when there are multiple IP adresses behind a domain name making the management of proxy/firewall more difficult and sometimes impossible (on some entry-level solutions). 

    Besides this, all other issues we encountered have been adressed by the Sugar team.

    Kind regards,

    Vlad TANASOIU / Synolia

Children
No Data