Skip to content

Python SDK is a connector library for the insanely fast HEXONET Backend API.

License

Notifications You must be signed in to change notification settings

centralnicgroup-opensource/rtldev-middleware-python-sdk

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ffe2dbc · Apr 29, 2020
Jan 24, 2020
Apr 29, 2020
Apr 29, 2020
Apr 1, 2019
Mar 11, 2020
Apr 29, 2020
Oct 31, 2018
Jul 12, 2018
Mar 11, 2020
Mar 11, 2020
Jul 31, 2018
Oct 31, 2018
Apr 29, 2020
Oct 31, 2018
Jul 6, 2018
Apr 29, 2020
Jul 12, 2018
Mar 11, 2020
Apr 15, 2020
Oct 31, 2018
Apr 1, 2019
Mar 11, 2020

Repository files navigation

python-sdk

semantic-release Build Status PyPI - Python Version PyPI Documentation Status License: MIT PRs welcome

This module is a connector library for the insanely fast HEXONET Backend API. For further informations visit our homepage and do not hesitate to contact us.

Resources

Features

  • Automatic IDN Domain name conversion to punycode (our API accepts only punycode format in commands)
  • Allows nested associative arrays in API commands to improve for bulk parameters
  • Connecting and communication with our API
  • Several ways to access and deal with response data
  • Getting the command again returned together with the response
  • Sessionless communication
  • Session based communication
  • Possibility to save API session identifier in PHP session
  • Configure a Proxy for API communication
  • Configure a Referer for API communication
  • High Performance Proxy Setup

High Performance Proxy Setup

Long distances to our main data center in Germany may result in high network latencies. If you encounter such problems, we highly recommend to use this setup, as it uses persistent connections to our API server and the overhead for connection establishments is omitted.

Step 1: Required Apache2 packages / modules

At least Apache version 2.2.9 is required.

The following Apache2 modules must be installed and activated:

proxy.conf
proxy.load
proxy_http.load
ssl.conf # for HTTPs connection to our API server
ssl.load # for HTTPs connection to our API server

Step 2: Apache configuration

An example Apache configuration with binding to localhost:

<VirtualHost 127.0.0.1:80>
    ServerAdmin webmaster@localhost
    ServerSignature Off
    SSLProxyEngine on
    ProxyPass /api/call.cgi https://api.ispapi.net/api/call.cgi min=1 max=2
    <Proxy *>
        Order Deny,Allow
        Deny from none
        Allow from all
    </Proxy>
</VirtualHost>

After saving your configuration changes please restart the Apache webserver.

Step 3: Using this setup

from hexonet.apiconnector.apiclient import APIClient as AC

cl = AC()
cl.useOTESystem()
cl.useHighPerformanceConnectionSetup() # Default Connection Setup would be used otherwise by default
cl.setCredentials('test.user', 'test.passw0rd')
r = cl.request({"COMMAND" => "StatusAccount"})

So, what happens in code behind the scenes? We communicate with localhost (so our proxy setup) that passes the requests to the HEXONET API. Of course we can't activate this setup by default as it is based on Steps 1 and 2. Otherwise connecting to our API wouldn't work.

Just in case the above port or ip address can't be used, use function setURL instead to set a different URL / Port. http://127.0.0.1/api/call.cgi is the default URL for the High Performance Proxy Setup. e.g. $cl->setURL("http://127.0.0.1:8765/api/call.cgi"); would change the port. Configure that port also in the Apache Configuration (-> Step 2)!

Don't use https for that setup as it leads to slowing things down as of the https overhead of securing the connection. In this setup we just connect to localhost, so no direct outgoing network traffic using http. The apache configuration finally takes care passing it to https for the final communication to the HEXONET API.

How to use this module in your project

All you need to know, can be found here.

Contributing

Please read our development guide for details on our code of conduct, and the process for submitting pull requests to us.

pip3 install -e .

Authors

List of responsible developers can be found here

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT License - see the LICENSE file for details.