Hi Fred,
thanks for the feedback.
> 1ct) is it possible to keep urllib2 as a fallback in the code? I guess a
> simple solution would be to bundle the functions in the webservice
> module into a class "RESTAPI". Depending on the availability of pycurl
> we could load one or the other - that's what the dynamic class loader is
> for :)
That is how it is currently implemented. ;-) It uses the pycurl dbs3 client and the fallback is urllib2. I just need to put the dbs3-client stuff somewhere in the repository. pycurl is available, if the script is executed in a cms environment.
> and the second
>
> 1ct) did you try the same benchmark with the "requests" lib
> (
http://docs.python-requests.org/en/latest/) ? I've found some
> indications that it might support ssl session caching as well (not on
> the homepage but on a stackoverflow page). Since pyCurl depends on a C
> lib, bundling requests (apache 2.0) would be a more deployment friendly
> solution, which would work everywhere …
No, I did not try the same benchmark with requests lib. However, I can do it and check whether ssl session caching is available as well. I doubt it.
I know packaging pycurl within grid-control will break the os independence of grid-control. Sourcing a cms environment would work and if that is not possible we will still have urllib2 as fallback. Probably, I would add a warning/notification in that case, so that people can choose.
Cheers,
Manuel